-
Notifications
You must be signed in to change notification settings - Fork 8
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
Update for new header #194
base: main
Are you sure you want to change the base?
Conversation
This reverts commit 6da3e50.
</j:if> | ||
<script src="${resURL}/plugin/customizable-header/js/messages.js" type="text/javascript"></script> |
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.
should that not stay on the line it had been , since you only want to import the js when you are using it.enabled
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.
Thinking was that you might want system messages without changing anything else about the header.
return header; | ||
} | ||
return new JenkinsHeaderSelector(); | ||
// TODO - come back to 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.
TODO.
} | ||
} | ||
|
||
// TODO - this should be combined with CustomHeaderConfiguration#401 |
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.
TODO
.collect(Collectors.toList()); | ||
} | ||
|
||
// TODO - this should be combined with CustomHeaderConfiguration#407 |
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.
TODO
Outside of the TODOs remaining, any thoughts on this @mawinter69? |
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'm not sure if it makes sense to keep the title
field with this header. Both are now put inside the logo.jelly which is inside the link to the Jenkins root.
<j:if test="${link.type == 'link'}"> | ||
<a href="${link.url}" class="jenkins-dropdown__item"> | ||
<div class="jenkins-dropdown__item__icon"> | ||
<j:out value="${link.iconXml}" escapeText="false" /> |
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.
iconXML might not be defined, e.g. when the chosen image is not a symbol but a simple png
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.
Actually the content aware header previously still allowed to define a default logo. So what we would need is more something like a logo behaviour (static, content aware (with the suboptions to show the weather). I even have some branch with a random logo where I used all the SVG found at https://www.jenkins.io/artwork/
This PR updates the plugin to be compatible with the [new Jenkins header]. The thinking behind this PR is to minimise the need for completely overriding the header, instead relying on replaceable slots in core's header. This will make it easier to update core in the future, without risk of breaking/impacting this plugin.
I've also added some examples themes to the plugin, demonstrating it's customizability and also making it easy for users to revert to the classic header theme if they prefer.
Testing done
Submitter checklist