-
-
Notifications
You must be signed in to change notification settings - Fork 28
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
Legend 2: Create legend components #2443
Legend 2: Create legend components #2443
Conversation
new AssetColorPalette( | ||
_.extend( | ||
assetConfig.colorPalette, | ||
_.pick(assetConfig, "label"), |
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.
If I understand, here we pass on the layer's label to overwrite the name of the property that is displayed in the legend. Why are we doing this? We may want to display the name of the property that is actually shown in the legend, or use the label that is configured in the colorPalette
config.
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.
Ah yea I saw that palette's label is currently not used so I assumed it's safe to override. But I just noticed that it's mentioned in ColorPaletteConfig so other portals might have it configured. I updated it to use the layer label only if a label is not set in the color palette config.
95f4e04
to
901e4b5
Compare
Co-authored-by: Robyn <[email protected]>
Co-authored-by: Robyn <[email protected]>
These scoped type names are used inconsistently throughout the code base and violate lint rules. I will not attempt a fix in this PR, and hold off until we have an agreed upon approach.
2c14302
to
43bdf9f
Compare
No description provided.