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

docs: add FAQ page and native features question #979

Merged
merged 2 commits into from
Jun 2, 2022

Conversation

mdjastrzebski
Copy link
Member

Summary

Adds FAQ page to the docs and provides answer to question about testing native features in RNTL.

Test plan

None

The the negative side:

- you cannot test native features
- certain JavaScript features might not be perfectly simulated by we are working on it
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd suggest adding a couple of examples (some people not well versed on the difference between native/js might struggle to figure out this barrier).

For instance, [react-native's ScrollView](https://reactnative.dev/docs/scrollview) has several props that depend on native calls. While you can trigger `onScroll` call with `fireEvent.scroll`, `onMomentumScrollBegin` is called from the native side and will therefore not be called.

Copy link
Member Author

@mdjastrzebski mdjastrzebski Jun 2, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@AugustinLF I've added the example you mentioned.

Copy link
Member

@thymikee thymikee left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚀

@thymikee thymikee merged commit 597fa3c into main Jun 2, 2022
@thymikee thymikee deleted the docs/faq-native-features branch June 2, 2022 12:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants