-
-
Notifications
You must be signed in to change notification settings - Fork 20
[WiP] [JENKINS-28728]: Support Pretty JSON outputs #19
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
base: master
Are you sure you want to change the base?
Conversation
|
@oleg-nenashev @jtnord Your review would be useful |
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.
Please avoid empty-line changes
|
The behavior should be optional, because non-pretty JSONs are preferable for the automated processing. I would propose to pass the mode via an additional enum-based parameter (d.g. mode=json, json-pretty, xml), which would alter the behavior of |
…ure that maps are serialized the same way
|
@oleg-nenashev @jtnord Your review would be useful, thanks in advance. |
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 would throw an error in the case of the unsupported format
|
👍 for the concept, noted minor improvement proposals in the code |
|
@oleg-nenashev I've reviewed your last recommendations. |
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 would also keep it in enum class, but it's optional at the current stage
|
@recena Thanks a lot for the adjustments. In the pull-request description I've noted several UI/UX-related things, which would be useful to address in this pull request. BTW, we can do it later. |
…uires pretty output
|
@oleg-nenashev I've reviewed the last adjustments. |
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.
why the object type and not the primitive?
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.
@rsandell Done.
|
public boolean isPretty() other than that :+1 |
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.
and the format of format is...
|
@oleg-nenashev This was a previous step before adding new documentation related to new formats. What do you thing about it? |
|
@oleg-nenashev I don't know what you mean with UI hyperlinks should return the data in pretty format by details ("raw data" links from container and image pages). Could you put an example? |
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.
Weak 👎 on this CSS in the plugin. If you want to add specific highlighting, it's better to create appropriate controls in Jenkins core. These styles may be an interim solution only
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.
- Could you tell if exist another plugin that includes its own API documentation?
- This change is not only highlighting, it also includes semantic in the markup
- There are a lot of plugins that includes its own CSS style in jelly templates
- If Jenkins Core includes a proposal to attend this, I'll remove the local CSS styles
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.
Sorry, I've missed the comment somehow. I propose to decouple the help formatting to a separate pull request, because it requires additional discussion and does not block the main proposed functionality.
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.
@oleg-nenashev Before revert my work (and throw my time to the trash), I'd like to know your technical reasons why you reject this.
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.
@recena
Just to clarify... I don't propose to throw your work to trash. I just propose to submit it as a separate pull request in order to review it separately from the functional changes.
|
@recena |
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 don't see a need in such change, but I'm OK to replace it.
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.
@oleg-nenashev I don't remember why, but I had to change this for any reason.
|
Hi @recena So, now we just need to finish the action items, merge the PR with the current branch and then squash commits. |
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.
The description below describes the structure of the json field. The new formatting may be quite confusing, a text should be adjusted at least
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.
@oleg-nenashev I'll take a look.
|
@oleg-nenashev As I said in above comment, if Jenkins core provides a global proposal for that, I'll send a new PR to review it. |
|
@oleg-nenashev I hope to send new modifications as soon as possible |
|
CC @alexanderrtaylor. BTW I feel it's stuck |
|
Two years ago... |
|
Sorry @recena I am looking it over now. Can you re-trigger the tests though? They are still showing as "pending" |
alexanderrtaylor
left a comment
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.
Pending a successful rebuild this Looks good and works for me locally
|
@alexanderrtaylor I'll take a look later. |

README.md