Skip to content

Repo: Enable strict & stylistic configs internally #6827

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

Closed
JoshuaKGoldberg opened this issue Apr 3, 2023 · 0 comments · Fixed by #7339
Closed

Repo: Enable strict & stylistic configs internally #6827

JoshuaKGoldberg opened this issue Apr 3, 2023 · 0 comments · Fixed by #7339
Labels
accepting prs Go ahead, send a pull request that resolves this issue repo maintenance things to do with maintenance of the repo, and not with code/docs

Comments

@JoshuaKGoldberg
Copy link
Member

JoshuaKGoldberg commented Apr 3, 2023

Suggestion

Labeling this in the v6 milestone because if we go for this, I'd like it to be used as dogfood / real world user feedback. Similar benefits tracked in #6759, so removing this from the v6 milestone.

Right now in our internal ESLint config we just enable recommended-type-checked: 5346b5b

It'd sure be nice if we used our own strict & stylistic configs!

@JoshuaKGoldberg JoshuaKGoldberg added triage Waiting for team members to take a look repo maintenance things to do with maintenance of the repo, and not with code/docs labels Apr 3, 2023
@JoshuaKGoldberg JoshuaKGoldberg added this to the 6.0.0 milestone Apr 3, 2023
@JoshuaKGoldberg JoshuaKGoldberg added accepting prs Go ahead, send a pull request that resolves this issue and removed triage Waiting for team members to take a look labels Apr 15, 2023
@JoshuaKGoldberg JoshuaKGoldberg removed this from the 6.0.0 milestone Jun 15, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 27, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
accepting prs Go ahead, send a pull request that resolves this issue repo maintenance things to do with maintenance of the repo, and not with code/docs
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant