-
Notifications
You must be signed in to change notification settings - Fork 20
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
Unused Stapler Facet is removed #121
Conversation
@timja I am on the fence about this. What do you think? |
Sounds fine to remove if it’s not being used, but not too familiar with this |
OK. We should probably do it. It is unlikely that this Facet was ever used in the field by anybody but me. |
Added some unit tests, and fixed two issues:
|
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.
A few minor suggestions.
I've confirmed the test fail and that changes in Jexl Inspection fix them. I have a hard time reasoning about this thing, so this is as best I can do in a limited time.
Oh boy! I built a local version of the next release. Ran the JEXL inspection on @jenkinsci/jenkins . It crashes in two files and shows 11 errors in 9 files. 4 has to do with localization. The rest is about HTML-encoded angle bracket 🤔 |
@duemir : this means as jexl inspection is now activated by default, it displays proper expected errors, but also points out some faulty plugin code (crashes) ? |
@jgreffe Yes, as far as I can see. I will try to iron at least some out. |
Crashes occur with i18n like:
|
Fixes #87
Remove all classes related to Facet
Remove all plugin.xml declarations related to Facet
Fixes infinite loop in
JexlInspection.tokenize("'")
: case${%Test('
Fixes out of range issue with patterns like
${%Test(something)}
(Argument rangeInElement (20,21) endOffset must not exceed descriptor text range (121, 141) length (20)
)Upgrading to this new plugin version on existing projects having facet will popup a warning message: