Expose registries. #830
Merged
Expose registries. #830
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
manthey
force-pushed
the
expose-registries
branch
from
c456694 to
1b2d7cf
Compare
This, or some other way, is needed to that if a feature is available in multiple renderers, so that a compound feature doesn't have to invoke a secondary renderer if the current renderer is sufficient (see the change for the annotationLayer, for instance). This also has the virtue that the geo.registries entry can be inspected to discover available features, layers, etc.
manthey
force-pushed
the
expose-registries
branch
from
1b2d7cf to
c0ab444
Compare
aashish24
approved these changes
Jun 1, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This, or some other way, is needed to that if a feature is available in multiple renderers, so that a compound feature doesn't have to invoke a secondary renderer if the current renderer is sufficient (see the change for the annotationLayer, for instance).
This also has the virtue that the
geo.registriesentry can be inspected to discover available features, layers, etc.