-
Notifications
You must be signed in to change notification settings - Fork 9
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
Pre commit full #30
Pre commit full #30
Conversation
I agree... the pre-commit file as it is in the project was only for my usage so I don't have to format the code manually. Extending and enforcing it globally needs approval also from @praiskup and @FrostyX. But since we don't plan to make changes in this repo this week we could discuss it next Tuesday on mtg |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wow, impressive!
Agreed with @nikromen to discuss this PR on the next meeting.
I will review it in detail on Monday.
Thank you for the changes @jpodivin,
Are any other formatting options available or this is the standard? :-) There are some minor things like But I don't really mind. Adhering to any standard is better than chaos. |
Standard is a loaded term. PEP8 is sometimes considered a standard, but even the PEP8 itself states that it shouldn't be taken slavishly [0]. This is one of the reasons I, personally, don't like opinionated linters. In fact they can become a detriment. As they kick in the moment you hit My recommendation would be:
[0] https://peps.python.org/pep-0008/#a-foolish-consistency-is-the-hobgoblin-of-little-minds |
sum up from what we agreed on the meeting:
I think this is close to what you Jirko suggested. Could you please update the PR? |
I don't have an opinion on this, both 100 or 88 is ok with me :D |
Signed-off-by: Jiri Podivin <[email protected]>
yaml linter allows for multiple documents in a single file package json files are now skipped by json pretty linter, as it is too opinionated closed tags in frontend layout Signed-off-by: Jiri Podivin <[email protected]>
Opinionated formatters were removed, the line length limit was increased to 100 chars. Signed-off-by: Jiri Podivin <[email protected]>
83f182c
to
733bb58
Compare
Final patch takes these into account. Github checks should sync with the new settings automatically starting with this PR. |
@nikromen you understand this much better than me. Can you please review if this matches what we wanted and merge if yes? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
All currently defined linters were applied to the repo and exclusion pattern was removed to make sure we maintain this level of coverage.
In several cases, the linters were not behaving in a sensible manner and their settings had to be adjusted.
This PR should be considered with care, because once established the standard of code may be difficult to change.