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

Move from standard to neostandard #136

Open
vweevers opened this issue Jun 9, 2024 · 1 comment
Open

Move from standard to neostandard #136

vweevers opened this issue Jun 9, 2024 · 1 comment
Labels
discussion Discussion maintenance General maintenance

Comments

@vweevers
Copy link
Member

vweevers commented Jun 9, 2024

See neostandard and context.

I'll have to get over my dislike of dangling comma's and I will, because the point of a code style is to avoid bikeshedding. That's the main strength of standard, so let's align with the kind folks who are keeping it alive.

I do want to wait for a self-contained CLI to become available (neostandard/neostandard#2) because I agree with neostandard/neostandard#2 (comment) and we're not really blocked here (standard works fine if you don't use typescript).

@vweevers vweevers added discussion Discussion maintenance General maintenance labels Jun 9, 2024
@voxpelli
Copy link

voxpelli commented Jul 4, 2024

Another vote for neostandard/neostandard#79 I see

Not sure when we will get a CLI solution, I do want to look into aligning that with ESLint and eg xo, especially to avoid having to release custom editor integrations neostandard/neostandard#33

Feedback etc is welcome 🙏

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion Discussion maintenance General maintenance
Projects
None yet
Development

No branches or pull requests

2 participants