Wait for camera initialization before carrying out queryRegion
#120
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Ensures that zoom will be present - Avoids potential NaN value for level and subsequently, chunk keys
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ |
Shane98c
approved these changes
Jun 17, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR sets up a
this.cameraInitializedpromise to track whether the camera values have been set for the first time, and then waits for that promise to resolve before carrying out any tile querying inthis.queryRegion(). This prevents the following error from being thrown because of bad key computation due to emptythis.zoom, which could occur when aRasterwas initialized with an open region picker.NaNvalue forthis.levelgetTilesOfRegion()that containNaNs!this.tiles[key].hasLoadedChunks(chunks)with a non-existent key