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

PR to resolve remaining warnings left in eslint #116

Merged
merged 16 commits into from
Mar 15, 2024

Conversation

shellyear
Copy link
Collaborator

Note: There are no actual eslint errors remained, but the other ones described here

@shellyear shellyear mentioned this pull request Mar 8, 2024
5 tasks
@shellyear shellyear force-pushed the fix/remaining-eslint-warnings branch from b694788 to 39df32f Compare March 8, 2024 10:50
@shellyear
Copy link
Collaborator Author

terminal after running npm run validate

I suggest to solve the chunk size warning in a separate branch. Created issue for that

Screenshot 2024-03-08 at 11 34 55

@shellyear shellyear force-pushed the fix/remaining-eslint-warnings branch 2 times, most recently from a91693e to 1b0fd3d Compare March 8, 2024 19:50
Copy link

@blcham blcham left a comment

Choose a reason for hiding this comment

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

Nicely separated commits 🥇. My comments mostly suggest adding some information to the found issues -- so they are trackable.

vite.config.js Outdated Show resolved Hide resolved
vite.config.js Outdated Show resolved Hide resolved
vite.config.js Outdated
@@ -14,6 +15,7 @@ export default defineConfig({
eslintPlugin({
cache: false, // disable eslint cache to avoid conflicts
}),
nodePolyfills(),
Copy link

Choose a reason for hiding this comment

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

Are we able to describe what is the issue? We could reference not only issue but also what causes it

It seems that it is again related to lib parse-link-headers. We can discuss alternatives to this library. Maybe some fixed fork?

Copy link

Choose a reason for hiding this comment

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

again we need to reference here issue which we can watch to solve the issue

Copy link
Collaborator Author

@shellyear shellyear Mar 13, 2024

Choose a reason for hiding this comment

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

@blcham got rid of that plugin, also it was not official. Solved in this commit

@blcham blcham self-requested a review March 13, 2024 12:40
vite.config.js Show resolved Hide resolved
vite.config.js Outdated Show resolved Hide resolved
@blcham blcham self-requested a review March 13, 2024 13:11
vite.config.js Outdated Show resolved Hide resolved
vite.config.js Outdated
@@ -14,6 +15,7 @@ export default defineConfig({
eslintPlugin({
cache: false, // disable eslint cache to avoid conflicts
}),
nodePolyfills(),
Copy link

Choose a reason for hiding this comment

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

again we need to reference here issue which we can watch to solve the issue

vite.config.js Outdated Show resolved Hide resolved
index.html Show resolved Hide resolved
@shellyear shellyear force-pushed the fix/remaining-eslint-warnings branch 2 times, most recently from 4f27b91 to f6ff982 Compare March 14, 2024 11:53
vite.config.js Outdated Show resolved Hide resolved
vite.config.js Outdated Show resolved Hide resolved
vite.config.js Show resolved Hide resolved
vite.config.js Outdated Show resolved Hide resolved
vite.config.js Outdated Show resolved Hide resolved
@shellyear shellyear force-pushed the fix/remaining-eslint-warnings branch from f7637c6 to f34ba50 Compare March 15, 2024 16:59
vite.config.js Outdated Show resolved Hide resolved
vite.config.js Outdated Show resolved Hide resolved
@blcham blcham merged commit 8a569ea into kbss-cvut:main Mar 15, 2024
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants