Skip to content
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

Prepare to remove several definitions in navActions. #4418

Merged
merged 29 commits into from
Jan 20, 2021

Conversation

chrisbobbe
Copy link
Contributor

Preparation for part of #4417.

We're in a React component that doesn't function as a "screen" component, so it doesn't automatically get the navigation prop.

  • These can often easily be converted to Hooks-based components, so that useNavigation can provide the navigation object.

This PR does those easy conversions to Hooks-based components. It also adds a type-wrapper and makes a tweak to the react-navigation libdef so that our use of useNavigation will be well-typed.

To make this possible, we also tweak `useNavigation` in the libdef
to make it generic.
I have *one* email notification about this log, from March 20, 2020,
but it's so old that it's already been cleared out of Sentry's
storage, it seems (the ID is a93f2c810f6647de93794db102f12488). And
searching Sentry for other events I might not have gotten an email
notification about...turns up empty.
No data was being grabbed with selectors, and `dispatch` wasn't
being used.
@chrisbobbe chrisbobbe requested a review from gnprice January 15, 2021 18:49
@gnprice gnprice merged commit ec6eaab into zulip:master Jan 20, 2021
@gnprice
Copy link
Member

gnprice commented Jan 20, 2021

Looks good, thanks! Merged.

@chrisbobbe chrisbobbe deleted the pr-prepare-remove-nav-actions branch November 4, 2021 22:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants