After AddMapLayerRequest fix #2361
Merged
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
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.
Some requests doesn't work properly if them are requested instantly after AddMapLayerRequest. Problems occur only when layer is added first time to map (DescribeLayer isn't loaded). The reason is that request handler tries to find layer from selected layers (not all available).
https://github.com/oskariorg/oskari-frontend/blob/master/bundles/mapping/mapmodule/request/map.layer.handler.js#L45-L62
Set opacity and style before request. Add option to rearrange layers after add is completed.