Repository navigation
fix(remix): linting issues in generated client init code - #949
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #949 +/- ##
==========================================
+ Coverage 24.24% 24.28% +0.03%
==========================================
Files 121 121
Lines 12877 12883 +6
Branches 713 715 +2
==========================================
+ Hits 3122 3128 +6
Misses 9734 9734
Partials 21 21
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
I advise against this. This is due to an upstream issue, see import-js/eslint-plugin-import#2969 |
|
Maybe it's fine idk |
s1gr1d
left a comment
There was a problem hiding this comment.
Just for some additional info around this: There is a bug in the eslint import/namespace package and that's the reason why we even have those warnings here. #949
However, as users are confronted with this warning right after they install Sentry I think importing it directly (not via the namespace) is a good workaround.
Closes https://linear.app/getsentry/issue/TET-74/[remix]-linting-errors-in-default-project-after-wizard