[JENKINS-60866] Make st:bind tag and JavaScript proxy work without inline JS - #385
Conversation
jglick
left a comment
There was a problem hiding this comment.
Do not recall well enough how st:bind works to offer a meaningful review
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
jglick
left a comment
There was a problem hiding this comment.
Not sure I follow well enough to review seriously.
This comment was marked as resolved.
This comment was marked as resolved.
jglick
left a comment
There was a problem hiding this comment.
Presuming someone else has done code review & testing on this & downstream, do you need a merge & release? It is not clear to me whether this is still a WiP or ready to go.
Thanks, just no good time IMO in the recent weeks. I'd like to be around for post-release support and ideally not simultaneously with another Stapler release. |
|
Last call for reviews :) |
jglick
left a comment
There was a problem hiding this comment.
Superficial comments, since I do not remember much about this system.
See JENKINS-60866.
Currently,
st:bindgenerates inline JS. This doesn't work with CSP, so move that out.Additionally, add a new
StaplerRequest#createJavaScriptProxyParametersas replacement forStaplerRequest#createJavaScriptProxythat can be used without needing toevalthe result.Downstream PR: jenkinsci/jenkins#6865