fix: parameterized disable_numparse for MarkdownTableSerializer #414
+9
−9
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.
This change introduces the
disable_table_numparseparameter toMarkdownParams, enabling it to be passed through to theexport_to_markdownfunction.When set to
True, this flag is forwarded to thetabulatefunction viadisable_numparse, preventing automatic numeric parsing.Previously, numeric values containing trailing zeros (e.g. "50.000") were automatically parsed and reformatted (e.g. to "50"), resulting in loss of precision in the Markdown table output. With this change, setting
disable_table_numparse=Truepreserves the original formatting of numeric strings during Markdown export.Issue ref: docling-project/docling#1891
By exposing this parameter, the implementation provides greater flexibility for different usage scenarios where numeric formatting preservation is required.