-
Notifications
You must be signed in to change notification settings - Fork 11
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
Enable IncorrectParamVarName
- Slight tightening of rules
#17
base: 8.x-2.x-civi
Are you sure you want to change the base?
Conversation
Per civicrm/civicrm-core#22515 there are a handful of these- we can fix the bulk of them pretty easily
On surface level, this makes sense and seems appropriate. On the substance... I'm a bit confused. I tried checking this out and running it against the files from civicrm/civicrm-core#22515 (ie the commit before
Additionally, I tried editing a I can confirm that I am really loading this ruleset - eg if I hack Possibly relevant:
If |
@totten so I did add it to my path per the install instructions
Ideally we would remove ALL the rules in the section that says I did try that & got a few too many changes to push up in one go - perhaps just removing 1 is a bit conservative but I did fix a few bits from it - but there might not be any / many left that cause this rule to get upset. If I let it run on the iats folder it fatals & there is something else somewhere causing problems (possibly bower_components) since I'm just running it in the civi-root |
Since I've installed into a buildkit folder rather than the global-composer, that translates for me to:
I can confirm that this causes it to pick up on I can confirm that upstream
-- I still don't see how this tightening is relevant to But don't get me wrong - if |
@totten yeah - lets merge it if it isnt failing anything for you. I already fixed all the things I found that failed with this - it's a pretty conservate hardening - but we can make go a bit further once it's locked in |
IncorrectParamVarName
- Slight tightening of rules
Per civicrm/civicrm-core#22515 there are a handful of these- we
can fix the bulk of them pretty easily