-
Notifications
You must be signed in to change notification settings - Fork 9
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
Make project_metadata mandatory in scan_request #316
Conversation
Step1 towards getting rid of meta. test plan: see related PR in semgrep-pro
Backwards compatibility summary:
|
Probably time to update this text to say 1.50.0 😄 |
semgrep_output_v1.atd
Outdated
project_metadata: project_metadata; (* replacing meta *) | ||
project_config: ci_config_from_repo; | ||
scan_metadata: scan_metadata; | ||
} |
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'll let you know when it's safe to roll this out. Not yet.
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've put back project_config as an option. There might not be a .semgrepconfig.yml in the repo so I think it's more logical to have an option here.
Note that the backward compatiblity failures are expected. We are breaking backward compatibility on purpose. |
try2 of #316 Step1 towards getting rid of meta. test plan: see related PR in semgrep-pro
new version in #324 |
try2 of #316 Step1 towards getting rid of meta. test plan: see related PR in semgrep-pro - [x] I ran `make setup && make` to update the generated code after editing a `.atd` file (TODO: have a CI check) - [x] I made sure we're still backward compatible with old versions of the CLI. For example, the Semgrep backend need to still be able to *consume* data generated by Semgrep 1.50.0. See https://atd.readthedocs.io/en/latest/atdgen-tutorial.html#smooth-protocol-upgrades Note that the types related to the semgrep-core JSON output or the semgrep-core RPC do not need to be backward compatible! --------- Co-authored-by: Clara McCreery <[email protected]>
Step1 towards getting rid of meta.
test plan:
see related PR in semgrep-pro
make setup && make
to update the generated code after editing a.atd
file (TODO: have a CI check)For example, the Semgrep backend need to still be able to consume data generated
by Semgrep 1.50.0.
See https://atd.readthedocs.io/en/latest/atdgen-tutorial.html#smooth-protocol-upgrades