Skip to content
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

feat(geo): manage layers and groups #1697

Draft
wants to merge 24 commits into
base: MSP-NEXT-TEMP
Choose a base branch
from

Conversation

alecarn
Copy link
Collaborator

@alecarn alecarn commented Sep 13, 2024

Breaking changes: This is a major refactor of the way we manage layer in IGO

  • New class 'LayerController' to manage layers and offer 3 types of layers, 'systemLayers', 'baseLayers', 'treeLayers'. The systemLayers is the drawing layer, measurement layer and other vital layers for the library. Note that a systemLayer can also be found in the treeLayers. The treeLayers is the hierarchical representation for the LayerViewer. The list of treeLayers can also be accessed under the flattened variant. Finally these three types of layers are aggregated to provide a unified list names 'all' which allows to have the 'baseLayers', 'systemLayers' and the flattened list of the 'treeLayers'

  • The way we access the layers has also changed, we must go through the LayerController

  • The LayerViewer does not allow to display the baseLayer, the 'excludeBaselayers' is removed

(cherry picked from commit 5ed250d6ca2b27d904de8d3354c11a981c64bf67)

@alecarn alecarn requested a review from pelord September 13, 2024 16:14
@alecarn alecarn self-assigned this Sep 13, 2024
@alecarn alecarn marked this pull request as draft September 13, 2024 16:15
@alecarn
Copy link
Collaborator Author

alecarn commented Sep 13, 2024

Je l'ai identifié comme DRAFT parce qu'on est en mode test de notre côté. Ça serait bien que tu jette un oeil en code review tout de même voir si la structure/design vous convient.

Breaking changes: This is a major refactor of the way we manage layer in IGO
- New class 'LayerController' to manage layers and offer 3 types of layers, 'systemLayers', 'baseLayers', 'treeLayers'. The systemLayers is the drawing layer, measurement layer and other vital layers for the library. Note that a systemLayer can also be found in the treeLayers. The treeLayers is the hierarchical representation for the LayerViewer. The list of treeLayers can also be accessed under the flattened variant. Finally these three types of layers are aggregated to provide a unified list names 'all' which allows to have the 'baseLayers', 'systemLayers' and the flattened list of the 'treeLayers'

- The way we access the layers has also changed, we must go through the LayerController

- The LayerViewer does not allow to display the baseLayer, the 'excludeBaselayers' is removed

(cherry picked from commit 5ed250d6ca2b27d904de8d3354c11a981c64bf67)

fix: lint

fix(geo): remove duplicate layer from all

(cherry picked from commit 42e4fa9b739c555f3c0f5b3a098ab14307aaae67)

fix(build): circular dependency revert compilationMode to full

fix(geo): circular dependencies
- refactor Layer/LayerGroup

fix(geo): time-filter-list remove BaseLayer

fix(geo): layer - project custom action in the bottom panel

refactor: change label for group

fix(geo): move layer with linkedLayers add system layer in tree

fix: any

chore: update packages

chore: update packages

fix: test

chore: fix path for build
The LayerController doest not reset all layers, the systemLayer are ignored
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant