You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the solution you'd like
CSpell is definitively a great tool to include inside a CICD
many CICD solution includes capability to report , track , issues leveraging the JUnit format
here leveraging Cspell reporter capability, the feature would be to add a Junit Reporter so thatn the output can be leveraged inside a CICD .
I started to work on a quite simple and crude implementation of a junit.xml reporter. See https://github.com/jkrenzer/cspell-junit-reporter for the source-code. Quite obviously I tried to stay as close to the cspell-json-reporter example as possible.
Currently Gitlab does read the generated files, but it is still very basic and the code is not stable. Use at your own risk, contributions are welcome.
Describe the solution you'd like
CSpell is definitively a great tool to include inside a CICD
many CICD solution includes capability to report , track , issues leveraging the JUnit format
here leveraging Cspell reporter capability, the feature would be to add a Junit Reporter so thatn the output can be leveraged inside a CICD .
junit format could be minimal like
Additional context
My context is about leveraging CSpell as a linter for Open API file
The text was updated successfully, but these errors were encountered: