-
-
Notifications
You must be signed in to change notification settings - Fork 3.3k
chore:Remove symlink in react query #9346
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
base: main
Are you sure you want to change the base?
chore:Remove symlink in react query #9346
Conversation
View your CI Pipeline Execution ↗ for commit c886b9e
☁️ Nx Cloud last updated this comment at |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #9346 +/- ##
===========================================
+ Coverage 45.39% 84.38% +38.99%
===========================================
Files 208 26 -182
Lines 8279 365 -7914
Branches 1872 107 -1765
===========================================
- Hits 3758 308 -3450
+ Misses 4080 48 -4032
+ Partials 441 9 -432 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we have the symlink in all other frameworks too so if we want to go that route, it would need to be addressed the same everywhere please, not just in the react adapter.
As mentioned in #9272, there were issues with configuration imports through symlinks.
While thinking about this problem, I came across the implementation of the react-router library. I found that this library solves the issue by simply importing with relative paths.
example
When I applied this approach to react-query and tested it on Windows, I confirmed that both ESLint and tsup work well.
If this PR gets merged, we should be able to remove other symlinks using the same approach as this PR. And it will enable development of tanstack query on Windows as well!