Skip to content
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

linter is not working properly in this repository #1239

Closed
benoitf opened this issue Jan 28, 2025 · 0 comments · Fixed by #1246
Closed

linter is not working properly in this repository #1239

benoitf opened this issue Jan 28, 2025 · 0 comments · Fixed by #1246
Assignees
Labels
area/ci kind/bug 🐞 Something isn't working

Comments

@benoitf
Copy link
Contributor

benoitf commented Jan 28, 2025

Bug description

I modified some svelte files and when running the pre-hook I got errors in svelte parsing file

I noticed also that the lint PR check rule is not checking the svelte file at all

Operating system

macOS

Version

next (development version)

Steps to reproduce

modify a svelte file and try to commit, see the error

Relevant log output

Additional context

No response

@benoitf benoitf added area/ci kind/bug 🐞 Something isn't working labels Jan 28, 2025
@deboer-tim deboer-tim self-assigned this Jan 29, 2025
deboer-tim added a commit that referenced this issue Jan 29, 2025
Tried making a few intentional mistakes, and yes, linting was very broken in
.ts and .svelte.

For consistency and picking a good baseline, I started by pulling the package.json
and eslint differences from the AI Lab extension, which included switching to the
newer eslint.config.mjs config instead of .eslint files. Eslint is updated, and
several plugins were added.

Since the rules in ai-lab are stricter than when eslint stopped working here,
this flagged ~160 'new' issues. This would be too much change for a single PR, so I
fixed all the minor/one-off issues here, disabled rules for the top 4, and opened
#1245 to enable them later.

Fixes #1239.

Signed-off-by: Tim deBoer <[email protected]>
@deboer-tim deboer-tim moved this to 🚥 In Review in Podman Desktop Planning OLD Jan 29, 2025
deboer-tim added a commit that referenced this issue Jan 29, 2025
Tried making a few intentional mistakes, and yes, linting was very broken in
.ts and .svelte.

For consistency and picking a good baseline, I started by pulling the package.json
and eslint differences from the AI Lab extension, which included switching to the
newer eslint.config.mjs config instead of .eslint files. Eslint is updated, and
several plugins were added.

Since the rules in ai-lab are stricter than when eslint stopped working here,
this flagged ~160 'new' issues. This would be too much change for a single PR, so I
fixed all the minor/one-off issues here, disabled rules for the top 4, and opened
#1245 to enable them later.

Fixes #1239.

Signed-off-by: Tim deBoer <[email protected]>
deboer-tim added a commit that referenced this issue Jan 29, 2025
Tried making a few intentional mistakes, and yes, linting was very broken in
.ts and .svelte.

For consistency and picking a good baseline, I started by pulling the package.json
and eslint differences from the AI Lab extension, which included switching to the
newer eslint.config.mjs config instead of .eslint files. Eslint is updated, and
several plugins were added.

Since the rules in ai-lab are stricter than when eslint stopped working here,
this flagged ~160 'new' issues. This would be too much change for a single PR, so I
fixed all the minor/one-off issues here, disabled rules for the top 4, and opened
#1245 to enable them later.

Fixes #1239.

Signed-off-by: Tim deBoer <[email protected]>
@github-project-automation github-project-automation bot moved this from 🚥 In Review to ✔️ Done in Podman Desktop Planning OLD Jan 29, 2025
@nichjones1 nichjones1 moved this to ✔️ Done in Podman Desktop Planning Feb 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/ci kind/bug 🐞 Something isn't working
Projects
Status: ✔️ Done
Development

Successfully merging a pull request may close this issue.

2 participants