Skip to content

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

Conversation

developer-bandi
Copy link
Contributor

@developer-bandi developer-bandi commented Mar 23, 2025

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[]>

@typescript-eslint
Copy link
Contributor

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.

@developer-bandi developer-bandi marked this pull request as draft March 23, 2025 15:00
Copy link

netlify bot commented Mar 23, 2025

Deploy Preview for typescript-eslint ready!

Name Link
🔨 Latest commit a4d1fb9
🔍 Latest deploy log https://app.netlify.com/projects/typescript-eslint/deploys/686aec061f7b300008bd6807
😎 Deploy Preview https://deploy-preview-10991--typescript-eslint.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 98 (no change from production)
Accessibility: 97 (🔴 down 3 from production)
Best Practices: 100 (no change from production)
SEO: 92 (🔴 down 8 from production)
PWA: 80 (no change from production)
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify project configuration.

Copy link

nx-cloud bot commented Mar 23, 2025

View your CI Pipeline Execution ↗ for commit a4d1fb9

Command Status Duration Result
nx run-many -t lint ✅ Succeeded 3m 16s View ↗
nx run-many -t typecheck ✅ Succeeded 2m 5s View ↗
nx test eslint-plugin-internal --coverage=false ✅ Succeeded 4s View ↗
nx test eslint-plugin --coverage=false ✅ Succeeded 3s View ↗
nx run integration-tests:test ✅ Succeeded 3s View ↗
nx run types:build ✅ Succeeded 5s View ↗
nx test typescript-estree --coverage=false ✅ Succeeded 1s View ↗
nx run generate-configs ✅ Succeeded 6s View ↗
Additional runs (27) ✅ Succeeded ... View ↗

☁️ Nx Cloud last updated this comment at 2025-07-06 21:40:35 UTC

@armano2
Copy link
Collaborator

armano2 commented Mar 23, 2025

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

@developer-bandi
Copy link
Contributor Author

developer-bandi commented Mar 24, 2025

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 Record<TabType,ErrorGroup[]> and displaying the corresponding error depending on the selected tab?

@developer-bandi developer-bandi marked this pull request as ready for review March 27, 2025 14:02
Copy link
Member

@JoshuaKGoldberg JoshuaKGoldberg left a 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.

Comment on lines +175 to +176
.split('\n')
.map((message: string) => {
Copy link
Member

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.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I'm not sure if this is realistic, but I used split because I was able to generate two errors with the settings below.

{
  "compilerOptions": {
    "moduleResolution": "classic",
    "resolveJsonModule": true,
    "incremental": true,
    "outFile": "dist/bundle.js"
  }
}
스크린샷 2025-04-12 오전 11 12 03

@JoshuaKGoldberg JoshuaKGoldberg added the awaiting response Issues waiting for a reply from the OP or another party label Mar 31, 2025
@github-actions github-actions bot removed the awaiting response Issues waiting for a reply from the OP or another party label Apr 12, 2025
@bradzacher bradzacher changed the title feat(website): Show tsconfig parsing errors in tab chore(website): Show tsconfig parsing errors in tab Jun 29, 2025
@kirkwaiblinger kirkwaiblinger changed the title chore(website): Show tsconfig parsing errors in tab chore(website): show tsconfig parsing errors in tab Jul 6, 2025
Copy link

codecov bot commented Jul 6, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.84%. Comparing base (7ec7931) to head (a4d1fb9).
Report is 4 commits behind head on main.

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           
Flag Coverage Δ
unittest 90.84% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Copy link
Member

@kirkwaiblinger kirkwaiblinger left a comment

Choose a reason for hiding this comment

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

Seems to work!

@JoshuaKGoldberg

@kirkwaiblinger kirkwaiblinger added the 1 approval >=1 team member has approved this PR; we're now leaving it open for more reviews before we merge label Jul 6, 2025
Copy link
Member

@JoshuaKGoldberg JoshuaKGoldberg left a comment

Choose a reason for hiding this comment

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

Lovely, thanks!

@JoshuaKGoldberg JoshuaKGoldberg merged commit 25728c2 into typescript-eslint:main Jul 7, 2025
62 of 64 checks passed
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 15, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
1 approval >=1 team member has approved this PR; we're now leaving it open for more reviews before we merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Enhancement: Display tsconfig errors in playground
4 participants