#10577: Fix - GFI in identify popup does not trigger when one of the responses is an error #10578
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
…hen one of the responses is an error
dsuren1
added
bug
BackportNeeded
MV88
approved these changes
Oct 2, 2024
|
@ElenaGallo please test it in DEV |
|
Test passed, @dsuren1 please backport to 2024.02.xx. Thanks |
dsuren1
added a commit
to dsuren1/MapStore2
that referenced
this pull request
Oct 3, 2024
…hen one of the responses is an error (geosolutions-it#10578) (cherry picked from commit 64474f4)
tdipisa
pushed a commit
that referenced
this pull request
Oct 8, 2024
tdipisa
removed
the
BackportNeeded
offtherailz
pushed a commit
that referenced
this pull request
Oct 18, 2024
…responses is an error (#10578)
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
This PR fixes the issue with GFI calls not triggered in identify popup when a request end up with an error response
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?
What is the new behavior?
The GFI calls are triggered correctly, even when one of the requests results in an error. The rest of the calls are executed and displayed properly in the identify panel (popup), and subsequent calls are also triggered correctly.
Breaking change
Does this PR introduce a breaking change? (check one with "x", remove the other)
Other useful information