-
-
Notifications
You must be signed in to change notification settings - Fork 27
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.
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
Unlock public collections for modifications #9
Comments
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently we're using some abstraction for enumeration of parsed items (projects, folders, dependencies, all others or most of this).
But v2 provides now analyzed map for some user modifications.
Basically,
Unlocking will give us more quick and convenient way for updating data. Because today's modifications mostly looks like extending its initial data, for example ~
But to keep it clean, more probably we also need to provide some information about modified state if it was.
What about simply flag state via our wrapped collection ? where add/remove/or even changing value of available items will expose an dirty state after its initial parsing ?
Option 1
draft
modified
state after changing its collections.Option 2
draft
Please feedback before my some final decision!
The text was updated successfully, but these errors were encountered: