Rename example files for zap-advanced to avoid docusaurus error #933
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Rami Souai <rami.souai@iteratec.com>
Signed-off-by: Rami Souai <rami.souai@iteratec.com>
J12934
approved these changes
Jan 17, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After updating Docusaurus to version 2.0.0-beta.14, an error is thrown during SSR if there are no TabItems with the default value. The Zap-Advanced docs page currently has no examples under "nginx" and "integration-tests" and therefore no tabs in the sections. A quick check in scanners/zap-advances/examples/nginx and integration-tests shows that the scan example file names deviate from the usual "scan.yaml" and thus aren't found during the docusaurus build, leading to this error:
Signed-off-by: Rami Souai rami.souai@iteratec.com
Description
Checklist
npm testruns for the whole project.