question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

If you’ve been testing out the V3 alpha, please post your issues here.

It’d also be good to know if V3 has fixed any existing issues you’ve had.

Reported issues

  • Remove engines from package.json (stupid yarn)
  • Unknown reorderId error when unmounting a group
  • Dragging to a space between items in another group should still place the item in this group
  • Auto-scroll toGroup when dragging to another group (not fromGroup)
  • Do not drag to new group if outside visible area (check root node collision)
  • Serious performance issues with 30+ reorder components
  • Inputs do not retain DOM state when dragging between lists
  • Gatsby window is not defined (move listeners to componentDidMount)
  • Avoid use of deprecated methods

Requested features

  • Option to start reorder only after movement
  • Handle / draggable area

Issue Analytics

  • State:open
  • Created 7 years ago
  • Reactions:5
  • Comments:47 (23 by maintainers)

github_iconTop GitHub Comments

1reaction
tmm1commented, Nov 15, 2020

FYI with v17 we need to rename to UNSAFE_componentWillMount:

react_devtools_backend.js:2430 Warning: componentWillMount has been renamed, and is not recommended for use. See https://fb.me/react-unsafe-component-lifecycles for details.

* Move code with side effects to componentDidMount, and set initial state in the constructor.
* Rename componentWillMount to UNSAFE_componentWillMount to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.

Please update the following components: Reorder
1reaction
JakeSidSmithcommented, Jun 6, 2018

@mcculloughjchris Merged #96 and published as 3.0.0-alpha.7. 🙂

Read more comments on GitHub >

github_iconTop Results From Across the Web

Predictive Maintenance Sensor V3 Alpha Station and Node ...
I'm having a few issues with Alpha Station and Node Red with the new PMS V3. I'm using the latest version of Alpha...
Read more >
Dyndolod 3 alpha's many issues : r/skyrimmods - Reddit
Dyndolod 3 alpha's many issues. I think these couple of images speak for themselves as to what my problems with Dyndolod are: ...
Read more >
Topics tagged v3-alpha - STORJ Forum
v3 -alpha ; My Node is OFFLINE for 2 hours · FAQ · v3-alpha , linux. 124, 16998, June 21, 2021 ; Failed...
Read more >
Mission Alpha: Frequently Asked Questions & Known Issues ...
The new Company of Heroes 3 – Mission Alpha application should be in your Steam library. Just download it and you'll be ready...
Read more >
Known issues for version 3.0 Alpha-1 - Joomla! Documentation
At this time, the following are known issues with Joomla! version 3.0 alpha-1. Cache is not cleared after changes made in back end....
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found