Draw

[VanshikaSabharwal]

This is a sub issue #35 of issue #29

I have added husky and pre-commits.

@dhruvpatidar359 you can merge husky for a consistent code workflow.

[vercel]

@VanshikaSabharwal is attempting to deploy a commit to the dhruvpatidar359's projects Team on Vercel.

A member of the Team first needs to authorize it.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
nextdraw	❌ Failed (Inspect)			May 16, 2024 8:59am

[VanshikaSabharwal]

hey @dhruvpatidar359 , Can you please merge my PR.

[dhruvpatidar359]

Actually there is some issue in the eslintsec.config file , which is causing the eslint check to not work in production . I have tried to resolve it , but failed will share that soon

…

On Tue, May 14, 2024, 7:12 PM Vanshika Sabharwal ***@***.***> wrote: hey @dhruvpatidar359 <https://github.com/dhruvpatidar359> , Can you please merge my PR. — Reply to this email directly, view it on GitHub <#37 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AYYPYM3CBR4YPEAOGNAWOX3ZCIIFJAVCNFSM6AAAAABHS4GTN6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJQGI4DAMRZGA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[VanshikaSabharwal]

Okay . Do tell me if any help needed @dhruvpatidar359 . I'll do my best

[dhruvpatidar359]

Okay . Do tell me if any help needed @dhruvpatidar359 . I'll do my best

Have a look 👀

[dhruvpatidar359]

Okay . Do tell me if any help needed @dhruvpatidar359 . I'll do my best

Have a look 👀

This was the original error

[dhruvpatidar359]

the deployment works well , but i think the eslint rules are breaking in this

[VanshikaSabharwal]

the deployment works well , but i think the eslint rules are breaking in this

Yes, Have you tried downloading @typescript-eslint/eslint-plugin?

[dhruvpatidar359]

may you please update the npm i @typescript-eslint/parser and add the package that u said . In the PR

[VanshikaSabharwal]

may you please update the npm i @typescript-eslint/parser and add the package that u said . In the PR

Okay, I am doing it

[VanshikaSabharwal]

I have installed @typescript-eslint/parser and @typescript-eslint/eslint-plugin. Good to go @dhruvpatidar359

[dhruvpatidar359]

i think still there is some issue with this .

[VanshikaSabharwal]

i think still there is some issue with this .

Hmm, I think this issue is due to

i think still there is some issue with this .

Prop type is not defined that is why the build failed.

The errors are indication that eslint is working fine and wants us to resolve every error in code.

[dhruvpatidar359]

@VanshikaSabharwal right now , i have merged your commits , directly into the master . So i can't merge this PR any more . What we can do is create a new PR again represeting the same issue . But with other code change if you can , but we can't add this code anymore . I will tag that PR as gssoc and level3 .

Actully i had to do that because , Props Type issue is not coming in the master , so i just cherry picked you commits and put those in the master . So don't worry , open a new PR i will merge it directly for you . 👩‍🚀