Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Introduce a new rule for naming style #44

Closed
shyiko opened this issue May 28, 2017 · 5 comments · Fixed by #1697
Closed

Introduce a new rule for naming style #44

shyiko opened this issue May 28, 2017 · 5 comments · Fixed by #1697

Comments

@shyiko
Copy link
Collaborator

shyiko commented May 28, 2017

This ticket is a parent for #27 #28 (PR available) #29 proposed by @iggymoran.

@shyiko
Copy link
Collaborator Author

shyiko commented May 30, 2017

Caution: these might not play well with kotlin-native (see https://github.com/JetBrains/kotlin-native/tree/master/samples).

@jzbrooks
Copy link

jzbrooks commented Sep 1, 2018

I have a few questions here @shyiko.

  1. Could you elaborate a little on why these rules might not play well with Kotlin Native?
  2. Is the current direction to make all of these name checks into a single rule, or would it be better that these are distinct rules?
  3. Would you consider adding a rule for constant values being UPPER_SNAKE_CASE?

@otaviocarvalho
Copy link

Any updates on that? @shyiko @iggymoran @jzbrooks

@romtsn romtsn changed the title Naming Introduce a new rule for naming style May 28, 2020
@rajalamourya
Copy link

Any update on this rule ? @shyiko

@paul-dingemans
Copy link
Collaborator

The current naming rule conventions seem quite clear and unambiguous. Some simple rules can be extracted quite simply from those conventions.

@paul-dingemans paul-dingemans added this to the 0.47.0 milestone Jun 27, 2022
@paul-dingemans paul-dingemans modified the milestones: 0.47.0, 0.48.0 Aug 14, 2022
paul-dingemans added a commit to paul-dingemans/ktlint that referenced this issue Nov 6, 2022
@paul-dingemans paul-dingemans mentioned this issue Nov 6, 2022
6 tasks
paul-dingemans added a commit that referenced this issue Nov 7, 2022
* Add naming rules for packages, classes, objects, functions and properties

Closes #44
# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants