-
Notifications
You must be signed in to change notification settings - Fork 409
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
#9466: handling GetFeatureInfo exceptions parameter format configuration #9471
Conversation
…iguration Desription: - put a default format for GFI exceptions - add getIdentifyFlow to catch GFI errors and exceptions
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.
@mahmoudadel54 it seems the unit test check is failing. Can you please check?
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.
Please:
getIdentifyFlow
should have a unit test that checks the effective output for exception.- the failing unit tests must be fixed
Description: fix unit test failing results, create new unit test for getIdentifyFlow for wms
sorry I sent my review to this PR in error, but the comment was for another pull request. 🤦 |
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.
a few things
the rest lgtm
add test cases for getIdentifyFlow in wms-test
edit in wms-test of mapInfo file by adding a unit test for exception
…g format for mapInfo/wms-test
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.
LGTM
@ElenaGallo Please test it in dev |
Test passe, @mahmoudadel54 please backport this to 2023.02.xx. Thanks |
…ion (#9471) (#9802) Co-authored-by: mahmoud adel <[email protected]>
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
#9466
What is the current behavior?
Some services has no "application/json" into their exception format list. So an exception of "Parameter 'exceptions' contains unacceptable value" shown for the GFI and prevent showing the identify results.
#
#9466
What is the new behavior?
There is no exception related to wrong exception format in GFI and identify works well with all WMS servcies including arcgis services and the identify results shown to user normally.
Breaking change
Does this PR introduce a breaking change? (check one with "x", remove the other)
Other useful information