-
Notifications
You must be signed in to change notification settings - Fork 7
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
Decide on line break convention to use for this repo and harmonise content #476
Comments
Decision on validator group meeting on October 15: Times well with #500 if there are not too many edits needed. Next step: @kalaspuffar to create a new branch off of guidelines-revision and introduce a testing tool used in the Dotify repository, which can check e.g. line break conventions. |
I've done some initial tests and the checkstyle plugin might not be the best fit. checkstyle/checkstyle#614 (comment) "Checkstyle have small team and a huge plans on extending for java language, and it should focus on one language, to be at the top among java analysers." |
@kalaspuffar do you think you'll find a solution for this that we can include in the release, or should we do this after the release? |
Hi @josteinaj I think you could release without this update, it will introduce a lot of changes and I have not yet found a good tool for verifying XML code styling. If you have any suggestions we could look into it. checkstyle could be modified to check XML but that is not optimal. Other tools usually pretty print XML files and that could be a solution as well, then again we need to be OK with the formatting that the tool is generating. Best regards |
I think we should postpone this to after the release. But let's discuss tomorrow. |
so that the editorconfig settings can be checked with Maven Related to #476
so that the editorconfig settings can be checked with Maven Related to #476
From the discussion on today's validation group meeting.
Subtasks:
The text was updated successfully, but these errors were encountered: