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.

Sign up for GitHub

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

Jump to bottom

findingsDetails are not printed correctly #20

Open
tomporat247 opened this issue Dec 28, 2021 · 3 comments
Open

findingsDetails are not printed correctly #20

tomporat247 opened this issue Dec 28, 2021 · 3 comments

Comments

@tomporat247
Copy link

probably a misusage of .tostring() instead of JSON.stringify().
Screen Shot 2021-12-28 at 14 40 34
@alexjurkiewicz
Copy link
Owner

Sounds like a great first issue for someone to contribute a fix for! hint hint ;)

@pzi
Copy link
Collaborator

pzi commented Jan 6, 2022 •
edited
Loading

Wondering if the contract has changed :) Looking forward to your PR to fix it! ;)

@pzi
Copy link
Collaborator

pzi commented Jan 6, 2022

After having a bit of a closer look and admittedly being a bit rusty on the script output, I don't see where in the script it would output/log <number> <lowercase severity> <full-stop>. You sure this is the correct repo and output from this action? Maybe add additional context?

@andrzej3393 andrzej3393 mentioned this issue Dec 21, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@alexjurkiewicz @pzi @tomporat247