Feature/#438 handle status updates (part 1) (!446) · Merge requests · ifs / geometalab / osmaxx · GitLab

GitLab now enforces expiry dates on tokens that originally had no set expiration date. Those tokens were given an expiration date of one year later. Please review your personal access tokens, project access tokens, and group access tokens to ensure you are aware of upcoming expirations. Administrators of GitLab can find more information on how to identify and mitigate interruption in our documentation.

Nicola Jordan requested to merge feature/#438-handle_status_updates-part_1 into combine_repos Apr 22, 2016

Created by: das-g

First part of #438 (closed):

Implemented in this PR:

If callback received and status in callback payload different from export model instance status:
1. update export model instance status
2. notify user by on-screen message
Share status definitions between conversion service and frontend

Still to do in subsequent PRs:

Query conversion service for jobs of state export statuses
Decide in more detail what should happen upon what status change (see https://github.com/geometalab/osmaxx-frontend/issues/438#issue-148772137) and implement that accordingly.
Remove status (field state) from extraction order model
Move downloads from extraction order model to export model

Reviewed by

@hixi

Please note

Export model statuses are initialized/set independent of extraction order status. So the information about the order's states will be lost when the corresponding field is removed in favor of the new field on the export model.