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

Improve some serialisation aspects of CSV fromat #315

Merged
merged 2 commits into from
Mar 1, 2024

Conversation

dabico
Copy link
Member

@dabico dabico commented Mar 1, 2024

Changes were made to both clean up the code, as well as increase the efficiency of the format by cutting down on redundant data. Although we still serialize nested objects in CSV as JSONs, we did change the list serialization format from a JSON String Array to a semicolon-delimited string format.

dabico added 2 commits March 1, 2024 14:11
I have no idea why we did this in the first place. I guess whoever
implemented this never bothered to check if the lists can be serialized
in CSV. By using the default serialization we also inadvertently save up
on space, as empty arrays will not be printed as `[]` to the CSV, but
rather a `null` in the form of an empty column value.
We removed both `GitRepoCsvDto` and its converter. I feel like an
inaccessible inner class is more fitting, since we can access the
`JsonMapper` from the outer class, and define the adepter code.
@dabico dabico merged commit 8d386fa into master Mar 1, 2024
5 checks passed
@dabico dabico deleted the enhancement/serialization branch March 1, 2024 21:45
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.

1 participant