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
create XSD definition for XML report #5166
Comments
unfortunately there is no xsd for result xml report, probably it was just forgotten to create. |
Thanks for an answer and approving my issue as a request 👍 |
good version to start.
|
@romani , I cannot. Simply, it's not mine asset. I pointed to it as it may be a nice starting point, but it is not under my control. (I had to have xsd file and that is what I found) also, as a first step IMO it's enough to have xsd even only in repo |
@rnveach , good point, CI will catch that. |
@romani |
ping @romani , any news on this ? :) |
Sorry, over occupied with active PRs, if you have time, please send PR, it will speed up the fix. |
I have no clue what is the report specification, that's exactly the thing I'm asking for |
@keradus If you mean the contents of the XML file to make the schema, you can look at our test expected outputs. |
sadly, i don't understand half of it (especially when you start raising bugs to it), be aware that I never played with checkstyle. |
please share a link to it, let us be aware of it and know how exactly it will benefit. For some legacy reasons we still use DTD , not xsd. So creation of xsd will be a bit unusual for us so please share where benefit is expected. |
the tool is PHP CS Fixer, which can report the outcome in different formats, one of requested by community is "checkstyle alike" |
Hi there! any update on this one? Would be great to finally have the format standardized! |
There are no updates as no one is working on this issue. You are welcome to help us with this. |
yet,
|
@keradus Since you have an XSD can't you apply it to all our expected outputs from our junits to verify it works for them? Our junit results should have all the expected formats. https://github.com/checkstyle/checkstyle/blob/master/src/test/resources/com/puppycrawl/tools/checkstyle/xmllogger/ExpectedXMLLoggerException2.xml https://github.com/checkstyle/checkstyle/blob/master/src/test/resources/com/puppycrawl/tools/checkstyle/ant/checkstyleanttask/ExpectedCheckstyleAntTaskXmlOutput.xml#L4 https://github.com/checkstyle/checkstyle/blob/master/src/test/resources/com/puppycrawl/tools/checkstyle/xmllogger/ExpectedXMLLoggerErrorModuleId.xml I'm not seeing anything wrong with it, but I've never worked with XSD much. Running against our junit results would be the best way to verify it. |
basically that would be... any java skills? ¯_(ツ)_/¯ let my say it once more, multiple CIs, like Jenkins, Sonar and so, may want to display report of checkstyle, but without knowing it's format, we always hit some edge cases that sth is there or not, because of assumptions that were made, because of missing spec |
Ok, looks like we do not have neither DTD not xsd for report, but have full coverage over configuration files https://github.com/checkstyle/checkstyle/tree/master/src/main/resources/com/puppycrawl/tools/checkstyle . |
@keradus , are be ok with DTD ? in report |
I, personally, would vote for XSD, if you ask me. Yet, ultimately, any standard scheme is good for that, DTD will work for me for sure 👍 |
@subkrish , can you help us with DTD creation for result XML report ? |
Hi
Checkstyle can produce a report used later in different Services, like Sonar, Jenkins and so.
Where can I find a xsd definition of that report ?
The text was updated successfully, but these errors were encountered: