Add XML linting and checking in CI pipeline
Issue/feature addressed
As XML files are often manually generated, errors and indentation inconsistencies are often introduced. This affect readability of the files.
Proposed solution
Add a XML linting and checking to the CI pipeline by using bash script.
Checklist
[] Functions and classes, or changes to them, are documented.[] User guide/documentation is updated.-
Changelog is updated. -
Suitable tests added for new functionality. -
Contributed code is correctly formatted. (See the contributing guidelines). [] License added to any new files.-
No extraneous files have been added (e.g. compiler output or test data files).
Warning
On the 19.07 the code formatting (code style) was standardised using clang-format, over the whole Nektar++ code. This means changes in your branch will conflict with formatting changes on the master
branch. To resolve these conflicts , see
#295 (closed)
Merge request reports
Activity
changed milestone to %v5.3.0
added 2 commits
marked the checklist item Contributed code is correctly formatted. (See the contributing guidelines). as completed
mentioned in issue #309 (closed)
I am trying to address the XML linting and checking issue. Bash files are used for that purpose as xmllint seems to offer little control over blank lines. The proposed approach ignore blank lines, i.e. leaves blank lines unchanged. Please let me know if you have any concerns with this implementation.
Edited by Jacques Xingadded build system label
assigned to @dmoxey
- Resolved by Chris Cantwell
- Resolved by Chris Cantwell
- Resolved by Chris Cantwell
- Resolved by Chris Cantwell