Skip to content

Removed linter warnings #820

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

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

shivasankaran18
Copy link

Related Issue : #771

I have removed all the linter warnings produced by the eslint .

@shivasankaran18
Copy link
Author

@ksen0 could you review the PR when you find the time?

@@ -0,0 +1,6 @@
#!/bin/sh
. "$(dirname "$0")/_/husky.sh"
Copy link
Contributor

Choose a reason for hiding this comment

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

It's a helpful PR to fix the linter warnings.
But I'm wondering, is husky required?

Copy link
Member

Choose a reason for hiding this comment

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

I agree, In the original discussion #771 I was suggesting removing existing linter warnings as a prerequisite for considering something like husky

Copy link
Member

@ksen0 ksen0 left a comment

Choose a reason for hiding this comment

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

Hi @shivasankaran18 , thanks a lot of these changes look really helpful! One minor question in the review; and could you please remove the updates to packages / remove husky from this commit? The intent was to separately remove existing issues, then add the automations. Because the 2.0 and main branches are used to deploy to 2 different sites (p5js.org and beta.p5js.org) so this will need to also be cherrypicked into 2.0, and automations shouldn't be added until linter warnings are removed on both sites

@@ -80,6 +57,31 @@ const SearchProvider = ({
}

if (!searchTerm) return;

const flattenData = (data: FuseResult<SearchResult>) => {
Copy link
Member

Choose a reason for hiding this comment

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

Could you explain why this one had to be moved, please?

@@ -0,0 +1,6 @@
#!/bin/sh
. "$(dirname "$0")/_/husky.sh"
Copy link
Member

Choose a reason for hiding this comment

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

I agree, In the original discussion #771 I was suggesting removing existing linter warnings as a prerequisite for considering something like husky

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.

3 participants