-
-
Notifications
You must be signed in to change notification settings - Fork 130
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
ImageryLayer readonly imageryProvider prop #664
Comments
TheMrCam
added a commit
to TheMrCam/resium
that referenced
this issue
Jun 21, 2024
Fixes lack of recreation on imageryProvider prop update by adding it to the cesiumReadonlyProps array, which is where it belongs according to the Cesium and Resium documentation. Addresses reearth#664
keiya01
added a commit
that referenced
this issue
Jul 9, 2024
* Fix ImageryLayer readonly imageryProvider prop Fixes lack of recreation on imageryProvider prop update by adding it to the cesiumReadonlyProps array, which is where it belongs according to the Cesium and Resium documentation. Addresses #664 * Remove unnecessary type definition --------- Co-authored-by: keiya sasaki <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Overview
The Resium docs and Cesium docs agree that
ImageryLayer#imageryProvider
is a readonly property.It appears that Resium does not accurately respect that, and as a result the
ImageryLayer
isn't being recreated on prop change.Is this an issue?
I primarily wanted to make this issue to ask permission to create a small PR that remedies the problem by moving
'imageryProvider'
fromotherProps
tocesiumReadonlyProps
, as I already have and use this as a custom Resium component downstream.However, there's entirely a chance that I'm actually missing something or doing something slightly incorrectly, in which case I wouldn't want to introduce any changes to Resium that would affect other developers.
The text was updated successfully, but these errors were encountered: