-
Notifications
You must be signed in to change notification settings - Fork 532
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
docs: remove help note for tf-plan.json restriction [CC-793] #1834
Conversation
32a8fe6
to
8bb11ca
Compare
@@ -61,6 +61,7 @@ function parseIacFileData(fileData: IacFileData): any[] { | |||
let yamlDocuments; | |||
|
|||
try { | |||
// the YAML library can parse both YAML and JSON content |
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.
Nice! Two last points now I read this again.
- Worth adding here that the reason we use YAML is it means we don't have to disambiguate between, JSON, single YAML doc and multiple YAML doc as the parser does it for us?
- In the spirit of the names of the other functions and to be explicit perhaps this should be called
parseYAMLOrJSONFileData()
to be clear that this will not support a terraform file for example.
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.
Is it a bit clearer now? I've tried to address both points, hopefully it makes sense 😃
This commit updates the snyk --help command to remove the note on the Terraform plan file name restriction [CC-793]
8bb11ca
to
0d729a4
Compare
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.
🙌 Looks amazing, thanks for iterating on the wording!
What does this PR do?
This PR updates the
snyk --help
command to remove the note about the Terraform plan file name restriction.Where should the reviewer start?
Have a look at the markdown document for any spelling mistakes.
How should this be manually tested?
Run
npm run generate-help
and have a look at the sections that changed.Any background context you want to provide?
The code changes were delivered under #1822.
What are the relevant tickets?
https://snyksec.atlassian.net/browse/CC-793
Screenshots