-
-
Notifications
You must be signed in to change notification settings - Fork 4.4k
deps(ui): Upgrade react aria April 2025 #87821
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
Conversation
Takes us from the September 30, 2024 Release to the March 5, 2025 Release. Some fixes for mergeProps and others might be the most interesting for us.
❌ 1 Tests Failed:
View the top 1 failed test(s) by shortest run time
To view more test analytics, go to the Test Analytics Dashboard |
# Conflicts: # package.json
This update will also fix: let me know if you need any help to get this over the finish line 🙏 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I left some suggestions on how to fix the new type errors without introducing a non-null assertion. I’ve basically taken them from here:
const focusedItem = state.collection.getItem(state.selectionManager.focusedKey)?.props | ||
const focusedItem = state.collection.getItem(state.selectionManager.focusedKey!)?.props |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
in the other PR I opened, I had fixed this differently without a no-null assertion:
const focusedItem: string | undefined = state.selectionManager.focusedKey
? state.collection.getItem(state.selectionManager.focusedKey)?.props?.value
: undefined;
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this isn’t resolved yet, we’re still using the no-null assertion here even though this is fixable with a runtime check
# Conflicts: # static/app/components/searchQueryBuilder/tokens/filterKeyListBox/index.tsx
static/app/components/searchQueryBuilder/tokens/filterKeyListBox/useFilterKeyListBox.tsx
Outdated
Show resolved
Hide resolved
…ox/useFilterKeyListBox.tsx Co-authored-by: Dominik Dorfmeister <dominik.dorfmeister@sentry.io>
Ah, we just merged these two little changes in: I think this means we need to update |
# Conflicts: # package.json
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚀
fixes DE-22 Takes us from the September 30, 2024 Release to the May 19, 2025 Release. Some fixes for mergeProps and others might be the most interesting for us. [changelog](https://react-spectrum.adobe.com/releases/index.html) --------- Co-authored-by: Malachi Willey <malwilley@gmail.com> Co-authored-by: Dominik Dorfmeister <dominik.dorfmeister@sentry.io>
fixes DE-22
Takes us from the September 30, 2024 Release to the May 19, 2025 Release. Some fixes for mergeProps and others might be the most interesting for us.
changelog