#12593 Improving Identify UX making some parameters configurable from UI#12609
Open
Binabh wants to merge 4 commits into
Open
#12593 Improving Identify UX making some parameters configurable from UI#12609Binabh wants to merge 4 commits into
Binabh wants to merge 4 commits into
Conversation
- Added FeatureInfoRequestOptions component to manage feature info settings. - Added WMS layer handling to preserve feature info configurations. - Added tests to validate new feature info options and their behavior. - Added translations for feature info request options in multiple languages.
6 tasks
Member
allyoucanmap
requested review from
stefanocudini
and removed request for
allyoucanmap
July 14, 2026 08:48
This file contains hidden or 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
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.
Description
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (check one with "x", remove the others)
Issue
What is the current behavior?
#12593
What is the new behavior?
Inputs have been added to catalog advanced settings for WMS layers and in layer settings. User can now input values there and that will be sent in
GetFeatureInforequest.Breaking change
Does this PR introduce a breaking change? (check one with "x", remove the other)