Open
Conversation
Makvagabo
approved these changes
Apr 4, 2022
Heymdall
approved these changes
Apr 4, 2022
aleksey-ilin
approved these changes
Apr 5, 2022
stepancar
approved these changes
Apr 5, 2022
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Добавление правила в eslint для именования enums
Мотивация и контекст
У нас на проектах кто-то использует UPPER_CASE, кто-то camelCase, кто-то PascalCase для енамом, предлагается следовать стандартной документации typescript и именовать enums в PascalCase
Данным правилом мы пытаемся стандартизировать написание свойств в енамах, вместо такого
Предлагаем писать в таком стиле
но данное правило пропускает такое написание