The nebula.gl project has migrated to deck.gl-community/editable-layers

uber / nebula.gl

A suite of 3D-enabled data editing overlays, suitable for deck.gl

https://nebula.gl/

Other

686 stars 166 forks source link

The nebula.gl project has migrated to deck.gl-community/editable-layers #902

Open ibgreen opened 4 months ago

ibgreen commented 4 months ago

nebula.gl has been forked into the deck.gl-community repo.

Future work will be done in https://visgl.github.io/deck.gl-community/docs/modules/editable-layers.
The new discussion channel for the deck.gl-community repo is in the OpenJS slack

cfecherolle commented 4 months ago

Hi! I was looking for a way to use https://www.npmjs.com/package/react-map-gl-draw with React 17 and react-map-gl but it's not compatible with React > 16, is this something that might be included in future work? Is react-map-gl-draw included in this fork? Thank you!

ibgreen commented 4 months ago

@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.

This decision was made to simplify the code base with the hope of making it easier for non-dedicated maintainers to keep the deck.gl layers version of nebula.gl alive.
Given that the new version is no longer broken into deck.gl independent modules, it may not be easy to add.

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.

timnyborg commented 4 months ago

@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?

ibgreen commented 4 months ago

do you have any intention of triaging the existing PRs on this rep

@timnyborg

I wish the core vis.gl team had the bandwidth to do that, but no. Simply getting the fork into a good shape has been heavy work for multiple contributors.
I also don't want to oversell the fork. While maintainers of other components have been willing to chip in and modernize build systems, dependencies etc, there is still no single thought leader or owner of the @deck.gl-community/editable-layers module, who can definitely answer whether a specific complex change is reasonable or not. This makes it harder to accept certain PRs etc.
So opening the same issues in the new repo is no guarantee of attention. However, the issues in this repo are almost certainly not going to be looked at.