React-sortable-tree: [Umbrella] Major bugs

[wuweiweiwu]

This is a umbrella issue to track major confirmed bugs that should be fixed ASAP. Feel free to comment to add more.

• [ ] #259
• [ ] #103
• [ ] #278
• [ ] #267
• [ ] #269
• [ ] #170
• [ ] #173
• [ ] #264

[buzztone]

@wuweiweiwu - I'd really like to see #173 added to this list.

It's a very significant problem for many of our users that fits, I think, very well with your plans "to clean up RST internal drag and drop management" mentioned at https://github.com/frontend-collective/react-sortable-tree/pull/285#issuecomment-386157745.

[wuweiweiwu]

Sounds good! Thanks @buzztone for bringing this to my attention

[lifejuggler]

@wuweiweiwu are you planning to leave these issues for this version and fix it on the next major version up?

[wuweiweiwu]

@lifejuggler that is the plan for now

[L0rdShrek]

Are there any new information for the bug #103

[NiketMalik]

Any update on issue https://github.com/frontend-collective/react-sortable-tree/issues/470

[fast0490f]

Please look this #665

[safinazward]

Any update on issue #278

[willopez]

665 causing problems for me too.

[jaydavid]

665 is causing issues for me as well

[deser]

Please add https://github.com/frontend-collective/react-sortable-tree/issues/821

[XYjourney]

Please add #821 not working in React 17.0.1

[datoslabs]

Hi,

Since issue #259 had been opened since 2018 and it's a major production issue for several others and myself; could someone please review the comments I have added and release a patch fix if possible? I encountered the bug with react 16.12 so I am not sure if the package.json fix mentioned recently will address this bug. However, I have done extensive tracing/debugging to outline what triggered the bug and shared my findings as well as the rationale for why the exception should be gracefully handled within try/catch block to "circumvent" the issue. Please let me know if you have any questions or concerns.