-
Notifications
You must be signed in to change notification settings - Fork 193
JS-824 Add rule S7639 #5919
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
JS-824 Add rule S7639 #5919
Conversation
|
Hi @loris-s-sonarsource - I think you need to sync rspec with your new rule in order for all of the build to work. EDIT: As written in chat, the rspec metadata.json is missing the |
|
@loris-s-sonarsource - you need to add the The jsons in the SonarJS repo will be copied over from rspec automatically. |
|
@zglicz ohhhh ok thank you !! I thought I could trick the system by directly uploading a correct json to this PR before merging my rspec PR |
No, sadly we cannot do that! Ideally, we wouldn't even store these json and htmls in git and just generate them on the fly. However, there are some tools like the rules.sonarsource.com or the rspec.sonar page that look into this exact folder from the git repo and expect these files to be present there. If they looked at the jar we would be fine, but they clone the repo and expect them tracked there. |
8ee3a20 to
a3cd221
Compare
|
A test is broken, but it seems that it's because of Next: |
vdiez
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.
LGTM, but I would recommend adding some sources for ruling tests in its/sources/jsts/custom, and adding the expected findings in its/ruling/src/test/expected/jsts/file-for-rules in lits format. Just to make sure the rule is executed during analysis
|
Noted, thank you! I am keeping that for my monday actions |
|




JS-824
Part of