-
Notifications
You must be signed in to change notification settings - Fork 8
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
Add extra parameter to transform or not html to markdown #205
Conversation
Co-authored-by: Philip Durbin <[email protected]>
Co-authored-by: Philip Durbin <[email protected]>
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.
This looks good! The only question I have is I don't see the test:coverage being run on the deploy action, should we add that?
Hmm, good question, I'm not sure about the test:coverage action here, maybe @GPortas has some insights about this? |
We discussed code coverage and created another issue to add it to Github actions. #208 |
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 good, approved!
Re-ran tests in Jenkins and did visual code inspection. No issues found - merging pr |
What this PR does / why we need it:
An additional parameter is added to the
getDataset
andgetPrivateUrlDataset
use cases to configure whether we want the values of the metadata fields containing html to be transformed into markup or not.Which issue(s) this PR closes:
Suggestions on how to test this:
Code visual inspection. Run tests.