Define how aspects and settings should be named

[coala-bot]

This should go into the documentation.

• An aspect should just talk about a property of something, not qualifying it. Don't name it TooLong but Length
• Then give it tastes, e.g. Metadata.CommitMessage.Shortlog.Length can have a taste named max_shortlog_length

About tastes:

• Do not use "allow" or "check", aspects can be turned on or off but tastes should change behaviour.
• For bool: use "shortlog_colon" if it must have a colon in the shortlog. Describe the thing that should be true: "shortlog_starts_upper_case". Give as much context as needed but not more.

Opened via gitter by @sils

[SiddharthKumar02]

@sils Should I create a new "Aspects and settings" file in the documentation? Because I can't seem to find a relevant file in the documentation to add these changes

[Techievena]

@SiddharthKumar02 Are you still working on this issue? 😄

[sils]

unassigning due to inactivity

[EverWinter23]

So, where should I add this information?

[sils]

I guess putting it on api.coala.io would be good, i.e. in the devdocs of the API

[userzimmermann]

I changed settings --> tastes in the issue summary and hope that this change will also happen soon to coala/cEPs#67 :)

[Techievena]

@EverWinter23 Please continue your work on this PR. We really need to have solid definitions of aspects and tastes for removing all kind of discrepancies while implementing aspects in coala.