-
Notifications
You must be signed in to change notification settings - Fork 410
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
Externalized in epic getFeatureInfo retrieval logic #3616
Externalized in epic getFeatureInfo retrieval logic #3616
Conversation
panelClassName: "modal-dialog info-panel modal-content", | ||
headerClassName: "modal-header", | ||
bodyClassName: "modal-body info-wrap", | ||
dock: true, | ||
headerGlyph: "", | ||
closeGlyph: "1-close", | ||
className: "square-button", | ||
allowMultiselection: false, |
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.
I would not remove this without an explicit reason.
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.
I partially maintained it (that it means that is not configurable anymore, but the code base for this flag is still maintained and tested).
Ideally, after this changes, it should go in the application state.
If you want I can finalize the support for this flag in the mapInfo state.
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.
Description
This pull request moves the request build and trigger logic from the FeatureInfoContainer to the
identify
epic. ThisThis refactor is required to allow clicked feature highlight (#3617)
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (check one with "x", remove the others)
What is the current behavior? (You can also link to an open issue here)
No changes
What is the new behavior?
Same as before. The only difference is about multiSelection (disabled by default:
multiSelection
flag is has been moved temporary from the Component configuration onto the action (is not configurable, we need a little more work to make configurable from the app state, but I didn't want to complicate things forc125_annotations
merge too much, for a feature that is not used neither documented).Does this PR introduce a breaking change? (check one with "x", remove the other)