Markdown capability for coverage comparison reports#90
Merged
sweco merged 1 commit intoslidoapp:mainfrom Oct 24, 2025
Merged
Conversation
Collaborator
Contributor
Author
|
No problem @sweco - What's the rejection message you're getting? Are you trying to clone my fork of the dbt-coverage repo? |
This changes the output format argument from cov_format to output_format.
Collaborator
|
Thanks for checking this @vvvito. In the end, my push command was incorrect, that's why it got rejected. |
This file contains hidden or 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
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.

Resolves #88
Added the ability to convert the string formatted comparison report into a markdown compliant format.
Useful for CI/CD pipelines and fills out the feature, as
computecommand has markdown capability, butcomparedidn't.Main changes:
CoverageFormatenum name to just 'Format' and reused it across thecompare/computefunctions.CoverageDiffdataclass that holds the passed inFormat, defaults toFormat.STRING_TABLEinstead ofFormat.MARKDOWN_TABLEThe
stringversion of the report inherits the new styling of the box ASCII characters, but remains relatively unchanged, e.g.:How to invoke
We can now use a new option with the
comparecommand called ``--compare-format`Which will output the following:
When converted into a markdown compliant editor:
dim.dim_core_patient_current_identifiersperson_idtac numberdim.dim_core_ordersname_cviddim.dim_core_patientsdate_of_birth_estimation_flagfamily_name_preferredmrn