-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
chore(website): show tsconfig parsing errors in tab #10991
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
chore(website): show tsconfig parsing errors in tab #10991
Conversation
Thanks for the PR, @developer-bandi! typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community. The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately. Thanks again! 🙏 Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently on https://opencollective.com/typescript-eslint. |
✅ Deploy Preview for typescript-eslint ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
View your CI Pipeline Execution ↗ for commit a4d1fb9
☁️ Nx Cloud last updated this comment at |
maybe we should just extends fs to contain info about errors for specific files, with that we could change/swap what we display based on file that is selected? tsconfig is a file (model) in monaco, similar to any other file, and its cloned as vfs file |
If I understand correctly, you mean changing the type of markers to |
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.
Thanks for getting this started! I think I found a bug? Also left a question and a few refactor suggestions.
.split('\n') | ||
.map((message: string) => { |
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.
Do you have an example of a message that needs to be split? I've only been able to make versions with a single reported error at a time.
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.
…loper-bandi/typescript-eslint into feature/tscofing-view-error
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #10991 +/- ##
=======================================
Coverage 90.84% 90.84%
=======================================
Files 501 501
Lines 50919 50919
Branches 8387 8387
=======================================
Hits 46256 46256
Misses 4648 4648
Partials 15 15
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 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.
Seems to work!
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.
Lovely, thanks!
25728c2
into
typescript-eslint:main
PR Checklist
Overview
I'm trying to manage tsconfig errors with different markers and statuses.Because I couldn't integrate tsconfig errors into markers since markers change depending on editor changes, and I thought it was wrong to apply tsconfig where markers are created.treat in below comment, change marker type to
Record<TabType,ErrorGroup[]>