feat: export data as json format #4779
Merged
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
…nto 2020-12-18-json-export
…nto 2020-12-18-json-export
…nto 2020-12-18-json-export
…nto 2020-12-18-json-export
djaiss
requested changes
Jan 5, 2022
|
@asbiin In an empty account, I added one contact, then exported my data in Json. It failed, and I have no idea why. |
I cannot reproduce it, it works fine with me. Don't you have any exception in your log file? |
djaiss
requested changes
Jan 11, 2022
Co-authored-by: Regis Freyd <[email protected]>
|
Kudos, SonarCloud Quality Gate passed! |
asbiin
changed the title
|
🎉 This PR is included in version 3.6.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
|
This pull request has been automatically locked since there |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 resolves #32
It's also related to #3104
It will also close #355
The idea is to export datas with json format, with a flat, simple structure
There are 1 root data "account" that contains "users", "contacts", and other datas for config: activityTypes, activityTypesCategories, etc.
All datas related to contact are detailed in the contact itself.
Photos and documents are serialized directly in the json file (which is not the case with the sql export)