-
Notifications
You must be signed in to change notification settings - Fork 16
PB-1383: External layers not loaded at startup #1507
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
PB-1383: External layers not loaded at startup #1507
Conversation
4e1969e to
9c90d98
Compare
pakb
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you also check a small bug I've seen while testing:
If you change the opacity of an external layer, then reload, the opacity is correctly applied only before the layer loads. It looks like the "after-load" actions are overwriting the opacity in the URL and set it back to the default value
This should be done with the following PR, I encountered the same bug while trying to fix the layers e2e tests. #1509 |
Issue: When trying to access the app, if there were external layers, they wouldn't be taken into account and not loaded. Fix: We remove a check that bypassed the addition of layers to the store at startup.
9c90d98 to
6824f36
Compare
Issue: When trying to access the app, if there were external layers, they wouldn't be taken into account and not loaded.
Fix: We remove a check that bypassed the addition of layers to the store at startup.
Test link