Fix #3224 Style Editor Plugin (GeoCSS)#3273
Fix #3224 Style Editor Plugin (GeoCSS)#3273allyoucanmap merged 12 commits intogeosolutions-it:c127_geonode_integrationfrom
Conversation
|
@allyoucanmap I see that we have the old WMSStyle functionalities replaced by the StyleEditor when StyleEditor is configured. |
|
problem: when the TOCItemSettings is "reset", but is locked (for example try to change the language while you are editing a style) the TOC is still locked, so you cannot do anything |
|
A question: I see that you cannot edit the default style, but you can edit available styles that are not the default, also if those are not created using the styler. Is this by design? |
|
When you create a new style as "Base SLD" you get an error from geoserver if you don't have the CSS module, because content-type is set to application/vnd.geoserver.geocss+css. |
|
Errors are not catched / shown properly when creating a new style, when GS security is not set properly you cannot create a style, but the user is not notified of the problem. |
mbarto
left a comment
There was a problem hiding this comment.
I am not able to do a real code review, such a big work cannot be just "read" and commented.
I downloaded the branch and did some hands-on testing, finding some issues, and I added comments for those.
I think big tasks like this one should be implemented by more than one person, so that a real code review can happen in real time, or we should commit them in small batches that a human can understand in a reasonable amount of time,
That said, I could not spot any particular error / issue during my reading, apart from the already mentioned comments.
Description
This PR will introduce Style Editor in GeoCSS and improve some components as TOCItemsSettings.
TOCItemsSettings improvements:
In addition a section of the state has been dedicated to additional layers.
Additional layers will override propertities of layers without modify the original layer object.
(see layerSelectorWithMarkers function in /selectors/layer.js)
Status docs and test:
Issues
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (check one with "x", remove the others)
What is the current behavior? (You can also link to an open issue here)
Issue #3224
What is the new behavior?
Does this PR introduce a breaking change? (check one with "x", remove the other)
If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information: