million
million copied to clipboard
feat: create linter
We currently use compiler warnings to mark deoptimizations / limitations. What if we created a ESLint plugin for better developing experience?
We currently use compiler warnings to mark deoptimizations / limitations. What if we created a ESLint plugin for better developing experience?
This will be a life-saver!!
/bounty $100
💎 $100 bounty • Million.js (YC W24)
Steps to solve:
-
Start working: Comment
/attempt #394
with your implementation plan -
Submit work: Create a pull request including
/claim #394
in the PR body to claim the bounty - Receive payment: 100% of the bounty is received 2-5 days post-reward. Make sure you are eligible for payouts
Thank you for contributing to aidenybai/million!
Add a bounty • Share on socials
Attempt | Started (GMT+0) | Solution |
---|---|---|
🟢 @adetoye-dev | Jul 17, 2023, 8:59:48 PM | WIP |
🟢 @hussainsaify17 | Dec 27, 2023, 6:00:29 AM | WIP |
🟢 @ancxanas | Feb 15, 2024, 10:34:52 AM | WIP |
Hi @aidenybai 👋
Would love to take on this, is there a deadline for completion??
Nope, there isn't. Go on ahead and take it @adetoye-dev!
Nope, there isn't. Go on ahead and take it @adetoye-dev!
Thanks Tobi 😊
I will take it
Go ahead @ehizman!
On it now!
/attempt #394
/attempt Let me work on this if still not resolved
I think it's safe to close this now @aidenybai. You have merged @Drex72's issue, right?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within the next 7 days.
@aidenybai can I take this up?
Hey this issue is closed ? I'm interested in working in this. And I do have some question.
- We need to publish eslint configs to npm and then use those custom eslint-rules.
- I can make skeleton with some predefined rules and then we can add those rules after discussion what react pattern are we targeting which needs user attention. /attempt #394
Options
[!NOTE] The user @adetoye-dev is already attempting to complete issue #394 and claim the bounty. We recommend checking in on @adetoye-dev's progress, and potentially collaborating, before starting a new solution.