-
Notifications
You must be signed in to change notification settings - Fork 0
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
add-editor-config #509
add-editor-config #509
Conversation
Signed-off-by: QuentinBisson <[email protected]>
@TheoBrigitte or @hervenicol could I have some eyes on the shellcheck fixes? |
Wow.... So, it's been decided that your editor could tamper grafana-exported dashboards at commit? I guess it's towards #502 . Most of these changes look legit, some will slightly change the script's behaviour but it looks like it was probably broken before. |
My understanding is that this PR is adding the editorconfig and pre-commit action but it's not enforcing a certain JSON style in CI, correct? |
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.
I think the change on helm/dashboards/values.schema.json
is problematic, as these files are usually generated using helm-schema-gen and that tool has its own indentation setting of 4 spaces. So updating the schema will become more painful.
If possible I would exclude this particular file and apply a different setting on it.
@hervenicol no this has not been decided at all :) we can discuss this 😅 |
5720304
to
688e56b
Compare
I removed shellcheck changes to keep the conversation to the main topic which is json formatting |
5124131
to
c04c77b
Compare
Signed-off-by: QuentinBisson <[email protected]>
c04c77b
to
e0c7da7
Compare
Team is not in favor of this, closing |
This PR
Checklist