Describe the bug
Not actually a bug, more a question - although it could be there is an issue with the Readme.md. In the ready me there is a warning right up on top:
Please note that this is not considered ready for production, as there are still a number of bugs being sent through.
But the project is now at v6.1.5. Does this statement still hold or is the readme.md nor up to date?
Expected behavior
I had expected anything > v1.0.0 was considered production ready.
Information
I really like this project, I have played with it before and being unhappy with the current implementation in our commercial app, I would like to consider this library better alternative.
I'm not looking for fellow developers opinions. I know there's probably a massive list of developers who've simply tried the lib and when it worked, it shipped. I'm also not looking for any guarantee's or accountability on stability. I'm simply looking for the perspective from the main contributors to this module...
Does the statement at the top of the readme.md still hold true? And the documented "problem" at the bottom of the readme.md for nested sorting with a shared state hook? If that was the only big issue regarding stability - cool, I can live with this.
Versions - Look in your package.json for this information:
react-sortable = ^6.1.5
react = ^18.0.0
Describe the bug
Not actually a bug, more a question - although it could be there is an issue with the Readme.md. In the ready me there is a warning right up on top:
But the project is now at v6.1.5. Does this statement still hold or is the readme.md nor up to date?
Expected behavior
I had expected anything > v1.0.0 was considered production ready.
Information
I really like this project, I have played with it before and being unhappy with the current implementation in our commercial app, I would like to consider this library better alternative.
I'm not looking for fellow developers opinions. I know there's probably a massive list of developers who've simply tried the lib and when it worked, it shipped. I'm also not looking for any guarantee's or accountability on stability. I'm simply looking for the perspective from the main contributors to this module...
Does the statement at the top of the readme.md still hold true? And the documented "problem" at the bottom of the readme.md for nested sorting with a shared state hook? If that was the only big issue regarding stability - cool, I can live with this.
Versions - Look in your
package.jsonfor this information:react-sortable = ^6.1.5
react = ^18.0.0