-
-
Notifications
You must be signed in to change notification settings - Fork 153
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
Version 1.0 release #230
Version 1.0 release #230
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
@bvaughn is there a possibility that you could consider putting back pixel constraints into the library in the future, given a simpler and more straightforward solution would be found? |
It's possible but it's not a priority for me. |
Are there any userland workarounds to be able to enforce minimum or maximum size in pixels? |
From the README on this PR: Can panel sizes be specified in pixels?No. Pixel-based constraints added significant complexity to the initialization and validation logic and so I've decided not to support them. You may be able to implement a version of this yourself following a pattern like this but it is not officially supported by this library. |
… Simplified some e2e tests by moving them into unit tests.
Checklist:
dataAttributes
prop with ...rest (to support all HTMLAttributes)dragState
is null #224I think this library's feature set is stable enough in my mind for a 1.0 release. It might be controversial but I have decided to cut pixel-based constraints from that release as they added too much complexity to the initialization and validation logic.