-
Notifications
You must be signed in to change notification settings - Fork 34
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
Replace more usage of deprecated APIs in map-layers #1177
Conversation
6de192e
to
617bd2f
Compare
@mdastous-bentley please check the PR description and confirm that's the intended behavior |
add a gif of your changes in dark mode, which often makes it easier to find bugs |
Added gif to the description. couldn't find a way to turn dark mode on test-viewer app. Haven't made any changes yet to that. wanted to confirm if that's the intended flow first. |
yes you should just need to pass in the theme prop to the viewer |
updated with gifs |
@hl662
You can delete a map layer source from list #1, and keep the "associated" map-layers attached in the viewport, no problem. All it means is that you won't be able to re-add by using the same map layer source later on. I don't think we want to mess with this actual design at this point. |
Got it. The design has been reverted back to this a couple commits ago |
Replace use of Popup in transparency popup
AttachMapLayerPopup is also refactored,
but needs more investigation into why the modal opens then closes immediately (event.stopPropagation isn't working well...). Relevant SO questionUpdate: The issue was when the modal opens from within the Popover's content, it's triggering state changes that affected the Popover's visibility. Fix- modified the state management to keep the Popover open while the MapUrlDialog modal is active - @pachhaibipin
TODOs:
Runpnpm test
, make sure to fix all testsRefactor SubLayersPopupButton to use iTwinUI's Popover.DISCUSSION:
if you look into the attached gif below, the attached map layer list does not get updated once we delete or edit the custom layer definitions. It didn't seem very intuitive. However, diving into the implementation, the code flow suggests once the layer is attached, it won't be updated with delete/edit action. Only way seems to be detaching it. Do we want to keep it that way? Should it detach/update the map layer list once we delete/edit the added definitions? wanted to confirm if that’s the intended flow @mdastous-bentley