Paths

Table of Contentst

-
native/
-
chat/
1/2
chat-router.js
1/2
chat.react.js
-
flow-typed/npm/@react-navigation/
-
npm/
-
@react-navigation/
1/2
bottom-tabs_v5.x.x.js
1/2
devtools_v5.x.x.js
-
material-top-tabs_v5.x.x.js
-
native_v5.x.x.js
-
stack_v5.x.x.js
-
navigation/
-
app-navigator.react.js
-
overlay-navigator.react.js
-
overlay-router.js
-
root-navigator.react.js
-
root-router.js
-
profile/
-
profile.react.js

[native] [9/34] ReactNav6: separate StackNavigationProp from StackNavigationHelpers
ClosedPublic
Actions

Authored by ashoat on Oct 20 2022, 6:12 AM.

Details

Reviewers

atul
tomek
bartek

Commits

rCOMMfdbe8fd2d6dd: [native] [9/34] ReactNav6: separate StackNavigationProp from…

Summary

We want to type setParams correctly for both the specific-screen and any-screen-on-a-navigator case. As a result, the type of setParams is incompatible between the two.

Note that I have left off setParams from NavigationHelpers in this diff. That's because I need to make some changes to our codebase before I can do that without leading to Flow errors... otherwise the two setParams will collide. I will reintroduce setParams to NavigationHelpers in a later diff in the stack.

Depends on D5401

Test Plan

Flow + ran the app on my phone and played around with it

Diff Detail

Repository

rCOMM Comm

Lint

Lint Not Applicable

Unit

Tests Not Applicable

Event Timeline

ashoat created this revision.Oct 20 2022, 6:12 AM

Herald added a subscriber: • abosh. · View Herald TranscriptOct 20 2022, 6:12 AM

ashoat added a child revision: D5403: [native] [10/34] ReactNav6: separate TabNavigationProp from TabNavigationHelpers.Oct 20 2022, 6:13 AM

ashoat mentioned this in D5406: [native] [13/34] ReactNav6: add setParams to NavigationHelpers.

Harbormaster completed remote builds in B12889: Diff 17680.Oct 20 2022, 6:34 AM

ashoat requested review of this revision.Oct 20 2022, 6:34 AM

atul accepted this revision.Oct 20 2022, 9:53 AM

This revision is now accepted and ready to land.Oct 20 2022, 9:53 AM

Closed by commit rCOMMfdbe8fd2d6dd: [native] [9/34] ReactNav6: separate StackNavigationProp from… (authored by ashoat). · Explain WhyOct 20 2022, 1:47 PM

This revision was automatically updated to reflect the committed changes.

ashoat added a commit: rCOMMfdbe8fd2d6dd: [native] [9/34] ReactNav6: separate StackNavigationProp from….

ashoat mentioned this in rCOMMb1015ced52d0: [native] [13/34] ReactNav6: add setParams to NavigationHelpers.

Revision Contents
Changeset List

Path

Size

native/

chat/

chat-router.js

8 lines

chat.react.js

21 lines

flow-typed/

npm/

@react-navigation/

bottom-tabs_v5.x.x.js

63 lines

devtools_v5.x.x.js

63 lines

material-top-tabs_v5.x.x.js

63 lines

native_v5.x.x.js

63 lines

stack_v5.x.x.js

65 lines

navigation/

app-navigator.react.js

9 lines

overlay-navigator.react.js

25 lines

overlay-router.js

8 lines

root-navigator.react.js

32 lines

root-router.js

8 lines

profile/

profile.react.js

3 lines

Diff 17765

View Options

native/chat/chat-router.js

	Show All 21 Lines
	a {			a {
	text-decoration: none;			text-decoration: none;
	color: #2a5db0;			color: #2a5db0;
	}			}
	img,			img,
	iframe {			iframe {
	display: block;			display: block;
	}			}
	input[type='text'],			input[type='text'],
	input[type='password'],			input[type='password'],
	textarea {			textarea {
	atulUnsubmitted Not Done Inline Actions Moving the global input styling and moving it to the input component. Then why are we keeping styles like `border` and `border-radius`? Don't these styles also affect the `<textarea>` tag? Are you sure we want to be removing these styles for that as well? Or should we break this into two separate selectors (one for `input` and another for `textarea`)? atul: > Moving the global input styling and moving it to the input component. Then why are we…
	benschacAuthorUnsubmitted Done Inline Actions Yeah, I should break these styles out a bit more. I don't think they really do anything. But you make a good point that this will also effect `textarea` elements. benschac: Yeah, I should break these styles out a bit more. I don't think they really do anything. But…
	-webkit-appearance: none;
	-moz-appearance: none;
	-webkit-border-radius: 0;
	border: 1px solid #dddddd;			border: 1px solid #dddddd;
	border-radius: 1px;			border-radius: 1px;
	font-family: var(--font-stack);			font-family: var(--font-stack);
	}			}
	:global(#react-root) {			:global(#react-root) {
	display: flex;			display: flex;
	flex-direction: column;			flex-direction: column;
	height: 100%;			height: 100%;
	▲ Show 20 Lines • Show All 243 Lines • Show Last 20 Lines

View Options

native/chat/chat.react.js

	Show All 21 Lines
	a {			a {
	text-decoration: none;			text-decoration: none;
	color: #2a5db0;			color: #2a5db0;
	}			}
	img,			img,
	iframe {			iframe {
	display: block;			display: block;
	}			}
	input[type='text'],			input[type='text'],
	input[type='password'],			input[type='password'],
	textarea {			textarea {
	atulUnsubmitted Not Done Inline Actions Moving the global input styling and moving it to the input component. Then why are we keeping styles like `border` and `border-radius`? Don't these styles also affect the `<textarea>` tag? Are you sure we want to be removing these styles for that as well? Or should we break this into two separate selectors (one for `input` and another for `textarea`)? atul: > Moving the global input styling and moving it to the input component. Then why are we…
	benschacAuthorUnsubmitted Done Inline Actions Yeah, I should break these styles out a bit more. I don't think they really do anything. But you make a good point that this will also effect `textarea` elements. benschac: Yeah, I should break these styles out a bit more. I don't think they really do anything. But…
	-webkit-appearance: none;
	-moz-appearance: none;
	-webkit-border-radius: 0;
	border: 1px solid #dddddd;			border: 1px solid #dddddd;
	border-radius: 1px;			border-radius: 1px;
	font-family: var(--font-stack);			font-family: var(--font-stack);
	}			}
	:global(#react-root) {			:global(#react-root) {
	display: flex;			display: flex;
	flex-direction: column;			flex-direction: column;
	height: 100%;			height: 100%;
	▲ Show 20 Lines • Show All 243 Lines • Show Last 20 Lines

View Options

native/flow-typed/npm/@react-navigation/bottom-tabs_v5.x.x.js

	Show All 21 Lines
	a {			a {
	text-decoration: none;			text-decoration: none;
	color: #2a5db0;			color: #2a5db0;
	}			}
	img,			img,
	iframe {			iframe {
	display: block;			display: block;
	}			}
	input[type='text'],			input[type='text'],
	input[type='password'],			input[type='password'],
	textarea {			textarea {
	atulUnsubmitted Not Done Inline Actions Moving the global input styling and moving it to the input component. Then why are we keeping styles like `border` and `border-radius`? Don't these styles also affect the `<textarea>` tag? Are you sure we want to be removing these styles for that as well? Or should we break this into two separate selectors (one for `input` and another for `textarea`)? atul: > Moving the global input styling and moving it to the input component. Then why are we…
	benschacAuthorUnsubmitted Done Inline Actions Yeah, I should break these styles out a bit more. I don't think they really do anything. But you make a good point that this will also effect `textarea` elements. benschac: Yeah, I should break these styles out a bit more. I don't think they really do anything. But…
	-webkit-appearance: none;
	-moz-appearance: none;
	-webkit-border-radius: 0;
	border: 1px solid #dddddd;			border: 1px solid #dddddd;
	border-radius: 1px;			border-radius: 1px;
	font-family: var(--font-stack);			font-family: var(--font-stack);
	}			}
	:global(#react-root) {			:global(#react-root) {
	display: flex;			display: flex;
	flex-direction: column;			flex-direction: column;
	height: 100%;			height: 100%;
	▲ Show 20 Lines • Show All 243 Lines • Show Last 20 Lines

View Options

native/flow-typed/npm/@react-navigation/devtools_v5.x.x.js

	Show All 21 Lines
	a {			a {
	text-decoration: none;			text-decoration: none;
	color: #2a5db0;			color: #2a5db0;
	}			}
	img,			img,
	iframe {			iframe {
	display: block;			display: block;
	}			}
	input[type='text'],			input[type='text'],
	input[type='password'],			input[type='password'],
	textarea {			textarea {
	atulUnsubmitted Not Done Inline Actions Moving the global input styling and moving it to the input component. Then why are we keeping styles like `border` and `border-radius`? Don't these styles also affect the `<textarea>` tag? Are you sure we want to be removing these styles for that as well? Or should we break this into two separate selectors (one for `input` and another for `textarea`)? atul: > Moving the global input styling and moving it to the input component. Then why are we…
	benschacAuthorUnsubmitted Done Inline Actions Yeah, I should break these styles out a bit more. I don't think they really do anything. But you make a good point that this will also effect `textarea` elements. benschac: Yeah, I should break these styles out a bit more. I don't think they really do anything. But…
	-webkit-appearance: none;
	-moz-appearance: none;
	-webkit-border-radius: 0;
	border: 1px solid #dddddd;			border: 1px solid #dddddd;
	border-radius: 1px;			border-radius: 1px;
	font-family: var(--font-stack);			font-family: var(--font-stack);
	}			}
	:global(#react-root) {			:global(#react-root) {
	display: flex;			display: flex;
	flex-direction: column;			flex-direction: column;
	height: 100%;			height: 100%;
	▲ Show 20 Lines • Show All 243 Lines • Show Last 20 Lines