-
Notifications
You must be signed in to change notification settings - Fork 166
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
The nebula.gl project has migrated to deck.gl-community/editable-layers #902
Comments
Hi! I was looking for a way to use https://www.npmjs.com/package/react-map-gl-draw with React 17 and |
@cfecherolle As you can read in the table in the linked deck.gl-community documentation page, react-map-gl-draw was not included in the fork.
If it helps, react-map-gl-draw is a small module and you could probably bring the source code into your app and bump the react dependency. |
@ibgreen do you have any intention of triaging the existing PRs on this repo, or should those of us with open fixes just port them across as new PRs on the deck.gl-community repo? |
|
Thanks for your work! So what would be the recommended approach for a new project using editable-layers with latest deck.gl v9? I'm not sure if the advances described at visgl/deck.gl-community#38 mean that editable-layers is functional from the new deck.gl-community repo. Should I go with the staled nebula.js EditableGeojsonLayer module or got with the new forked one? |
What we can say is:
|
nebula.gl has been forked into the deck.gl-community repo.
The text was updated successfully, but these errors were encountered: