-
Notifications
You must be signed in to change notification settings - Fork 24.4k
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
Flatten Text examples in RNTester to make them searchable #44518
Conversation
This pull request was exported from Phabricator. Differential Revision: D57197676 |
This pull request was exported from Phabricator. Differential Revision: D57197676 |
…4518) Summary: # Changelog: [Internal] - For some inexplicable reason, we had majority of `Text` test examples (42 out of 46) in RNTester stuffed into `<RNTesterBlock/>` components inside one huge "Basic" test case. This was highly imbalanced, introduced extra nesting, cluttering the UI, but most importantly, none of those 42 out 46 test cases were searchable for. This change flattens all of the corresponding nested test cases to the top level, making them into valid separate test cases, which are also searchable. It also corresponds to the general structure we have in other test examples, such as `TextInput`. Differential Revision: D57197676
This pull request was exported from Phabricator. Differential Revision: D57197676 |
This pull request has been merged in f8c1ad6. |
This pull request was successfully merged by @rshest in f8c1ad6. When will my fix make it into a release? | How to file a pick request? |
…4518) Summary: Pull Request resolved: facebook#44518 # Changelog: [Internal] - For some inexplicable reason, we had majority of `Text` test examples (42 out of 46) in RNTester stuffed into `<RNTesterBlock/>` components inside one huge "Basic" test case. This was highly imbalanced, introduced extra nesting, cluttering the UI, but most importantly, none of those 42 out 46 test cases were searchable for. This change flattens all of the corresponding nested test cases to the top level, making them into valid separate test cases, which are also searchable. It also corresponds to the general structure we have in other test examples, such as `TextInput`. Reviewed By: cipolleschi Differential Revision: D57197676 fbshipit-source-id: 777eb2aa238a91bb3f52d2f0ab10edc6bfad5c85
Summary:
Changelog:
[Internal] -
Differential Revision: D57197676