Fix import context with style (drawing layer) #1374
Merged
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.
Please check if the PR fulfills these requirements
What is the current behavior? (You can also link to an open issue here)
this behavior related to #1337
What is the new behavior?
1- Store the feature style as an igoStyleObject within _style property.
2- Store the label inside the _mapTitle property.
Overall, this PR propose to use existing mecanism to handle styles during import (context or data). This is a "temporary" fix. I think we need to create a new layer type or extend the vector type, to handle internal layer types (draw, directions, measures) to be handled easily, on export/import.
Furthermore, the style handling will be changed shortly by using the geostyler library.
Does this PR introduce a breaking change? (check one with "x")
If this PR contains a breaking change, please describe the impact and migration path for existing applications:
Other information: