Skip to content
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

handle one line blocks as regular blocks #35

Closed

Conversation

arielkru
Copy link
Contributor

@arielkru arielkru commented Jul 19, 2020

Parse one-line-blocks as regular blocks, so the parser's output for both types of blocks would be the same (values nested in lists)

Solves bridgecrewio/checkov#452

@aoskotsky-amplify

@arielkru arielkru changed the title handle one line blocks as regular blocks, by setting new lines inside… handle one line blocks as regular blocks Jul 19, 2020
@schosterbarak
Copy link

Hi @jconstance-amplify , @aoskotsky-amplify
any chance you can take a look at this one?

@@ -0,0 +1,67 @@
name: build
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this shouldn't be in this pr, its unrelated to the functionality of the fix, ie. its switching ci

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep. My bad. After waiting to get this one merged I created a temporal fork. Would gladly drop it when if the other changes in the PR looks good to the maintainers.

@@ -1,5 +1,5 @@
{
"name": "python-hcl2",
"name": "bc-python-hcl2",
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

your referencing your fork, instead of the upstream your contributing to.

@@ -35,7 +35,7 @@ def get_requirements():


setup(
name='python-hcl2',
name='bc-python-hcl2',
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

your referencing your fork, instead of the upstream your contributing to.

@aoskotsky-amplify
Copy link
Member

aoskotsky-amplify commented Oct 1, 2020

Merged this as part of #45. Thanks for sending this PR!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants