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

Manage conflicting import versions #113

Open
The4thLaw opened this issue Jan 30, 2021 · 0 comments
Open

Manage conflicting import versions #113

The4thLaw opened this issue Jan 30, 2021 · 0 comments
Labels
Milestone

Comments

@The4thLaw
Copy link
Owner

The4thLaw commented Jan 30, 2021

Description

The XML export files have a meta/version/@Schema field that allows identifying the schema with which an export was generated.

We should use this field to warn users when they import a version that is older than the current one. It should still be possible to run the import because chances are that it will work properly.

The warning should show the meta/version/@demyo field rather than the technical schema version.

Maybe we could check .dea files on the client side with a browser zip library (like zip.js). This would really ease the confirmation. This will only work if the zip file is not fully loaded in memory.

With that said, since the warning should be quite rare, we could ask the user to upload again if confirmation is needed.

@The4thLaw The4thLaw added impact:ui impact:backend impact:behind the scenes Issues that users would probably never notice prio:medium labels Jan 30, 2021
@The4thLaw The4thLaw added this to the v3.1.0 milestone Jan 30, 2021
The4thLaw added a commit that referenced this issue Jan 31, 2021
There is now issue #113 to track it.
@The4thLaw The4thLaw modified the milestones: v3.1.0, v3.2.0 Sep 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant