Skip to content

Conversation

@bvaughn
Copy link
Owner

@bvaughn bvaughn commented Dec 10, 2023

Checklist:

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

@vercel
Copy link

vercel bot commented Dec 10, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
react-resizable-panels ✅ Ready (Inspect) Visit Preview 💬 Add feedback Dec 13, 2023 2:51am

@tsufiev
Copy link

tsufiev commented Dec 11, 2023

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

@bvaughn
Copy link
Owner Author

bvaughn commented Dec 11, 2023

It's possible but it's not a priority for me.

@NMinhNguyen
Copy link

Are there any userland workarounds to be able to enforce minimum or maximum size in pixels?

@bvaughn
Copy link
Owner Author

bvaughn commented Dec 13, 2023

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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants