-
Notifications
You must be signed in to change notification settings - Fork 382
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
#10197: fix Skipping 'Configure Map' step breaks context configuration #10207
Conversation
…xt configuration - fix the issue of beak context due to missing map config in case of edit an existing context by skip map configure tab - write a unit test for this change
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 Fix works. However, can you please look into the suggestions below, thanks
…xt configuration Description: - resolve the review comments
@ElenaGallo Kindly test it in DEV and let us know if it can be backported. Thanks! |
Test passed, @mahmoudadel54 please backport to 2024.01.xx. Thanks |
…xt configuration (geosolutions-it#10207) * geosolutions-it#10197: fix Skipping 'Configure Map' step breaks context configuration - fix the issue of beak context due to missing map config in case of edit an existing context by skip map configure tab - write a unit test for this change * geosolutions-it#10197: fix Skipping 'Configure Map' step breaks context configuration Description: - resolve the review comments
|
#10207) (#10210) * #10197: fix Skipping 'Configure Map' step breaks context configuration - fix the issue of beak context due to missing map config in case of edit an existing context by skip map configure tab - write a unit test for this change * #10197: fix Skipping 'Configure Map' step breaks context configuration Description: - resolve the review comments
Description
In this PR: fixing the issue of beak context due to missing map config in case of edit an existing context by skip map configure tab
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (check one with "x", remove the others)
Issue
#10197
What is the current behavior?
#10197
What is the new behavior?
Editing an existing context by skip map configure tab is working without break context
Breaking change
Does this PR introduce a breaking change? (check one with "x", remove the other)
Other useful information