New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Save DB state to file #19

Open

GrafGenerator opened this issue Oct 7, 2016 · 1 comment

Labels

Owner

GrafGenerator commented Oct 7, 2016

Version 1.0.0 breaks DB data saving back to file because it uses only in memory DB.
This is good feature and it's worth to implement it.

Major questions:

Since plugin allows to merge many files into one DB, how to deal with this case? It's generally impossible to propagate DB changes back to appropriate file.
Server reloading works via gulp's watch, so modifying source file when reloading DB will cause server reloading again causing infinite cycle then.

The solution for both issues is to save bundled DB changes to one file, speficied in options for plugin.

GrafGenerator added the enhancement label

Owner Author

GrafGenerator commented Oct 7, 2016

The case with infinite reloading when one of watched source files specified as output file should be at one's own risk.

GrafGenerator mentioned this issue

Update json file #18

Closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment