-
Notifications
You must be signed in to change notification settings - Fork 465
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
Update starter import/export format to be json #19400
Comments
So from the description I think the plan is to still support the existing CSV format; but just to be clear - I think the import/export using CSV files will still need to be supported, because it's much, much easier for customers to export CSV files and work with them in a spreadsheet program than it would be for them to work with JSON files. So if we update the format, we'll need to have two separate/parallel import/export format readers/writers (one for CSV and one for JSON). But the underlying code which takes those results and does things like validate them can (and should) be shared for both formats. |
PR: #21236 |
* #19400 First commit on moving export files as json * #19400 New ImportStarter/ExportStarter implementation using json files * #19400 Rolling back last commit * #19400 Using JsonIgnoreProperties(ignoreUnknown = true) where needed * #19400 Adding support for importing/exporting ImmutableContentlet * #19400 Import/Export starter with JSON files * #19400 Cleaning up code * #19400 New starter based on JSON * #19400 New tests * Applying code review suggestions * #19400 Updating starter Co-authored-by: nollymar <nollymarlonga@Nollymars-MacBook-Pro-2.local>
Fixed, tested on release-22.07 // Docker // FF. Now we are able to start the server using a JSON format file as starter, but this is a breaking change, now we are unable to start using a previous starter. |
This is part of a bigger feature where the main goal is to avoid relying on Hibernate.
Acceptance criteria: Import/Export functionality should keep working as always
The text was updated successfully, but these errors were encountered: