fix: export of boolean fields in CSV files #374
Closed
Conversation
This file contains 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
danibix95
changed the title
danibix95
approved these changes
Sep 18, 2024
|
I have only one doubt in how to proceed 🤔 This change is actually a breaking change with respect to the previous behavior of the service. |
|
Eventually we decided to not merge this change to not cause a breaking in current export interface. We opted for another change on the component that was using this API. |
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.
Pull Request Type
Description
In this PR it is changed how boolean fields of documents are exported in CSV files. Indeed, now they are
represents as the strings
"true"and "false" instead of the previous values1and empty value `` respectively.PR Checklist
Does this PR introduce a breaking change?
Other information