We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Either:
@maplibre/maplibre-react-native
react-native
expo
I'm not sure yet if this is restricted to Android or due to a recent MLRN change.
In Typescript, a workaround is to cast the output of getPointInView to "unknown as [number, number]", i.e.
const mapViewPoint = mapViewReference.getPointInView(geographicCoordinates); return mapViewPoint as unknown as [number, number];
... And then just treat it as [number, number] or GeoJSON.Position
GeoJSON implies geographic coordinates, so I think [number, number] makes more sense.
The text was updated successfully, but these errors were encountered:
getPointInView
getCoordinateFromView
🎉 This issue has been resolved in version 10.0.0-beta.20 🎉
The release is available on:
Your semantic-release bot 📦🚀
Sorry, something went wrong.
No branches or pull requests
Steps to Trigger Behavior
Expected Behavior
Either:
Actual Behavior
Environment
@maplibre/maplibre-react-native
Version: 10.0.0-beta.19react-native
Version: 0.76.6expo
Version: 52.0.25Notes
I'm not sure yet if this is restricted to Android or due to a recent MLRN change.
In Typescript, a workaround is to cast the output of getPointInView to "unknown as [number, number]", i.e.
... And then just treat it as [number, number] or GeoJSON.Position
GeoJSON implies geographic coordinates, so I think [number, number] makes more sense.
The text was updated successfully, but these errors were encountered: