-
Notifications
You must be signed in to change notification settings - Fork 416
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
Problems with GeoStory map configurations merge process #10489
Closed
1 of 3 tasks
Comments
This was referenced Jul 24, 2024
12 tasks
@mahmoudadel54 this issue need to be evaluated and estimates. Then a fix provided directly within the connected PR here. |
@mahmoudadel54 you can proceed with this by updating the connected PR as requested. |
mahmoudadel54
added a commit
to mahmoudadel54/MapStore2
that referenced
this issue
Aug 21, 2024
…ry map configurations merge process Description: - fix issue of crash app in geostory if user edit layer properties of existing geostory - add unit tests due to changes
12 tasks
mahmoudadel54
added a commit
to mahmoudadel54/MapStore2
that referenced
this issue
Aug 28, 2024
…ry map configurations merge process Description: - implament new approach in onChange for Editor in MapEditor file to fix the app crash issue if user edit layer properties of existing geostory - remove the prev implemented approach - remove unused unit tests
mahmoudadel54
added a commit
to mahmoudadel54/MapStore2
that referenced
this issue
Aug 28, 2024
…ry map configurations merge process Description: - remove unused unit tests
mahmoudadel54
added a commit
to mahmoudadel54/MapStore2
that referenced
this issue
Sep 5, 2024
…ry map configurations merge process Description: - fix issue of crash app in geostory if user edit layer properties of existing geostory - add unit tests due to changes
mahmoudadel54
added a commit
to mahmoudadel54/MapStore2
that referenced
this issue
Sep 5, 2024
…ry map configurations merge process Description: - implament new approach in onChange for Editor in MapEditor file to fix the app crash issue if user edit layer properties of existing geostory - remove the prev implemented approach - remove unused unit tests
mahmoudadel54
added a commit
to mahmoudadel54/MapStore2
that referenced
this issue
Sep 5, 2024
…ry map configurations merge process Description: - remove unused unit tests
allyoucanmap
pushed a commit
that referenced
this issue
Sep 5, 2024
mahmoudadel54
added a commit
to mahmoudadel54/MapStore2
that referenced
this issue
Sep 11, 2024
…ations merge process (geosolutions-it#10516)
tdipisa
pushed a commit
that referenced
this issue
Sep 11, 2024
offtherailz
pushed a commit
that referenced
this issue
Oct 18, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Legacy geostories used following configuration to store the difference between original resources and changes made to a map in a specific section:
original map resource
diff section map configuration
The merging process of these two configuration has two steps:
This process had a problem in the step 1 because only null layers were converted but not group layers.
With the introduction of the new TOC the diff configuration for layers and groups was removed and this two field are cloned as soon there is a modification in the section. This introduced another problem described in this comment:
#10426 (comment)
In conclusin we need to solve the issues described above:
How to reproduce
Expected Result
The geostory should be visible and working
Current Result
The application show the error message on full screen
Browser info
(use this site: https://www.whatsmybrowser.org/ for non expert users)Other useful information
The text was updated successfully, but these errors were encountered: