Skip to content
This repository has been archived by the owner on Jul 15, 2023. It is now read-only.

Ease up on strictness in the default configs of naming rules #678

Closed
JoshuaKGoldberg opened this issue Dec 14, 2018 · 3 comments
Closed

Ease up on strictness in the default configs of naming rules #678

JoshuaKGoldberg opened this issue Dec 14, 2018 · 3 comments
Labels
Status: Accepting PRs Type: Breaking Change Type: Bug

Comments

@JoshuaKGoldberg
Copy link

Splitting off from @astorije's comment in #672: function-name suggesting static functions be UPPERCASE is odd and nonstandard behavior. That should not be enabled as part of the default configuration.

We should also double-check other rules to see if there are odd naming conventions espoused by their defaults.
@JoshuaKGoldberg JoshuaKGoldberg mentioned this issue Dec 14, 2018
Closed
@astorije
Copy link
Contributor

I'm fine with the strictness here btw, just this convention felt odd compared to what's out there.

@JoshuaKGoldberg JoshuaKGoldberg mentioned this issue Jun 28, 2019
Closed
@astorije
Copy link
Contributor

Porting here a suggestion from #822: making the allow-size-argument option of prefer-array-literal to be true by default.

@JoshuaKGoldberg
Copy link
Author

☠️ It's time! ☠️

Per #876, this repository is no longer accepting feature pull requests. TSLint is being deprecated and we recommend you switch to https://typescript-eslint.io.

Thanks for open sourcing with us, everyone!

# for free to subscribe to this conversation on GitHub. Already have an account? #.
Assignees
No one assigned
Labels
Status: Accepting PRs Type: Breaking Change Type: Bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@astorije @JoshuaKGoldberg