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

Exposed conditiion to report template and moved html encoding the TM.… #151

Merged
merged 1 commit into from
Apr 7, 2021

Conversation

nozmore
Copy link
Collaborator

@nozmore nozmore commented Apr 2, 2021

…report method

Initially I just wanted to expose Threat conditions to the report template but because HTML encoding was done when the threats were read in that would have broken eval logic. To address this I moved html encoding to the TM.report method and encode threat data from within the list of threats and findings.

With this change json output is json encoded but not html encoded and output to report used to generate the markdown file then html via pandoc is html encoded.

@nozmore nozmore requested a review from izar as a code owner April 2, 2021 21:46
@nozmore nozmore force-pushed the expose_condition branch from 9ff8245 to 85c1f23 Compare April 2, 2021 21:55
@ghost
Copy link

ghost commented Apr 2, 2021

DeepCode failed to analyze this pull request

Something went wrong despite trying multiple times, sorry about that.
Please comment this pull request with "Retry DeepCode" to manually retry, or contact us so that a human can look into the issue.

@izar izar merged commit da9df14 into master Apr 7, 2021
izar added a commit that referenced this pull request Apr 13, 2021
Fix encoding errors due to compatibility between #151 and #154
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