-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
[select] fix: mark items arrays as readonly where appropriate #5171
[select] fix: mark items arrays as readonly where appropriate #5171
Conversation
packages/docs-app/src/examples/select-examples/multiSelectExample.tsx
Outdated
Show resolved
Hide resolved
5ccb273
to
8fcd017
Compare
I have to revert this, it's causing downstream compilation errors:
|
@adidahiya curious if that's actually coming from using a I suspect it's probably the second looking at the file name. If that's the case, seems easy enough to only apply the change for types blueprint components use, and leave the exported types alone? |
It is the latter, "downstream consumer reusing |
hmmm, now that I think about it, my potential solution to that problem kinda falls under 'no one wins' territory since folks trying to get the actual prop types will have trouble. I think it makes sense to do this as a breaking change as a part of v5. That way we could also fix the callback types as well. What does queuing a change for v5 look like? |
I'm not ready for this yet, but i'll have a process for this ready in the next few weeks. Stay tuned |
Fixes #4976
Checklist
Changes proposed in this pull request:
Added readonly annotations to select array props
Reviewers should focus on:
The types
Screenshot