-
Notifications
You must be signed in to change notification settings - Fork 50
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
Refresh custom wms layer+source on update (issue 601) #631
Conversation
Signed-off-by: Quinn Guerin <[email protected]>
Signed-off-by: Quinn Guerin <[email protected]>
Signed-off-by: Quinn Guerin <[email protected]>
Signed-off-by: Quinn Guerin <[email protected]>
Thank you @qugu2427 for raising the PR, could you please add some test screenshot/video in this PR? |
@junqiu-lei sure, here is a video of the issue currently and with the refresh method |
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.
LGTM
The cypress failure of documentsLayer is due to CI runner capacity. |
Signed-off-by: Quinn Guerin <[email protected]> (cherry picked from commit 605e894)
Signed-off-by: Quinn Guerin <[email protected]> (cherry picked from commit 605e894)
Signed-off-by: Quinn Guerin <[email protected]> (cherry picked from commit 605e894) Co-authored-by: Quinn <[email protected]>
Description
UpdateLayerConfig()
is broken as per #601. Specifically, line 36maplibreInstance.style.sourceCaches[layerConfig.id].update(maplibreInstance.transform)
throws a object reference error. I suspectmaplibreInstance.transform
is gone by the time it's used. Additionally, there are alot of what seem to be workarounds in the function, namely calling seemingly private methods of MaplibreGL and a spelling mistake. While I am by no means familiar with this codebase, it seems that simply deleting and refreshing the layer+source would be a better option. Especially, since updating wms fields would require a full refresh of tiles anyway.Issues Resolved
#601
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.