Watching db.sqlite reloads on db save about generator-vars-django HOT 2 CLOSED

Thanks for the report. There isn't a use-case for watching the sqlite3 file :) It was part of patterns.core to begin with because it needed to be copied over to the build directory in the core task. While I don't think it should produce any unintended app behavior in a production environment because you wouldn't be watching files with Gulp then, I definitely agree that it is horribly wrong to watch sqlite3 files during development. That was unintended.

For the time being you can configure tasks/.taskconfig and change the watching entries for the core task. It's here:

...
watch: {
    entries: [{
      files: path.join(paths.src, '**', '*.' + patterns.core), // Modify this glob pattern(s), can be string or array
      tasks: ['core']
...

from generator-vars-django.

v3.0.6 (433fcfa) now has copying of db files as a separate task.

from generator-vars-django.