-
Notifications
You must be signed in to change notification settings - Fork 118
Add multiple manager support #941
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As discussed, the ID_GENERATOR
could be moved to either the child class or the CoreElementProvider
(and making the provider a field at the same time) in order to remove the roundtripping between parent and child.
Also, the layer/source ID could be stored permanently, per instance in a non-static field, so that getters don't require string concatenation.
2e97d48
to
7bc2f74
Compare
Consolidated everything inside concrete instances of CoreElementProvider. Ready for another round of 👀 . |
7bc2f74
to
e717e4e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A tiny bit more could've been moved to an abstract element provider, but generally LGTM 👍
In general yes, good to avoid duplication but since it's generated from a template file, updating code requires updating that one template file in a similar way as you would do with that abstract class. Developer flow wise that is kinda be the same. |
Closes #921