-
Notifications
You must be signed in to change notification settings - Fork 901
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
autolink scans non used components #2455
Labels
Comments
As for fix, either the cli would need to invoke the codegen, or at lease use the same rules as codegen.
|
There hasn't been any activity on this issue in the past 3 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 7 days. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Environment
Description
react-native 0.75-rc.4 uses
npx @react-native-community/cli config
to get components needed to autolink. Hovewer it just scans for all the folders for all source files, so it can find false positives. And it's hard to understand/troubleshoot what's going on.I've faced it when I've moved a non finished spec out of the folders I've specified , yet autolink was still referred to it. I thought that there was some cached state that caused the component to be searched for.
In the reproducer the cli will find and adds https://github.com/mfazekas/rn-075-autolink/blob/autolink-wrong-files/RTNCenteredText/temp/Playgroud.ts to autolink.
Reproducible Demo
The text was updated successfully, but these errors were encountered: