Skip to content

BGDIINF_SB-2792 : fix layer ordering#383

Merged
pakb merged 2 commits intodevelopfrom
bug-BGDIINF_SB-2792-layer_ordering
Mar 6, 2023
Merged

BGDIINF_SB-2792 : fix layer ordering#383
pakb merged 2 commits intodevelopfrom
bug-BGDIINF_SB-2792-layer_ordering

Conversation

@pakb
Copy link
Contributor

@pakb pakb commented Feb 24, 2023

There was a discrepancy between mf-geoadmin3 layer ordering (in the menu and URL) and web-mapviewer way of handling them. In the URL, layers should be ordered from bottom to top, and on the side menu from top to bottom (layer "on top" of the layer stack is the top layer). Topics were an issue as they list their layers to activate in the opposite order (top -> bottom) so I've inverted those layer before importing them.

Test link

@github-actions github-actions bot added the bug label Feb 24, 2023
@pakb pakb requested review from jedef and ltshb February 24, 2023 08:51
Copy link
Contributor

@jedef jedef left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a simple naming fix of a "data-cy" and its all good!

<PopoverButton
v-if="hasMultipleTimestamps"
ref="popover"
popover-position="left"
Copy link
Contributor

@jedef jedef Feb 24, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why do you want the popover to open on the left? Isn't it less practical as it hides the menu when the popover is open?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

that's to fix an issue with timestamp testing in Cypress, if set to auto (left untouched) it would go on the top position, and with the dev warning, Cypress considers that it is covered by the disclaimer and fails the test of visibility. That was an "easy" fix.
We could move it to the right though...

pakb added 2 commits March 6, 2023 10:18
There was a discrepancy between mf-geoadmin3 layer ordering (in the menu and URL) and web-mapviewer way of handling them.
In the URL, layers should be ordered from bottom to top, and on the side menu from top to bottom (layer "on top" of the layer stack is the top layer).
Topics were an issue as they list their layers to activate in the opposite order (top -> bottom) so I've inverted those layer before importing them.
instead change the e2e test to reflect the change of logic in layer ordering
@pakb pakb force-pushed the bug-BGDIINF_SB-2792-layer_ordering branch from 8f7d43d to f46c25b Compare March 6, 2023 12:57
@pakb pakb merged commit 6075f58 into develop Mar 6, 2023
@pakb pakb deleted the bug-BGDIINF_SB-2792-layer_ordering branch March 6, 2023 13:12
@pakb pakb mentioned this pull request May 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants