You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For a given application in version e.g. 0.0.1-dev, upload current api.json just with a new version 0.0.2-dev (and no other changes to api.json).
This causes a new entry in history (correct): <org>/<app>/0.0.2-dev | version changed from 0.0.1-dev to 0.0.2-dev
Then delete the current version (with Delete this version).
Go back to application history page. The above history entry version changed from 0.0.1-dev to 0.0.2-dev is still the last one, and there's no mention of deletion (and the fact that 0.0.2-dev no longer exists).
Proposal:
when version gets deleted, create new entry in history as: <org>/<app>/0.0.1-dev | deleted version 0.0.2-dev (proposal 1) or <org>/<app>/0.0.1-dev | deleted version 0.0.2-dev (now at 0.0.1-dev) (proposal 2)
The text was updated successfully, but these errors were encountered:
To reproduce:
For a given application in version e.g.
0.0.1-dev
, upload current api.json just with a new version0.0.2-dev
(and no other changes to api.json).This causes a new entry in history (correct):
<org>/<app>/0.0.2-dev | version changed from 0.0.1-dev to 0.0.2-dev
Then delete the current version (with
Delete this version
).Go back to application history page. The above history entry
version changed from 0.0.1-dev to 0.0.2-dev
is still the last one, and there's no mention of deletion (and the fact that0.0.2-dev
no longer exists).Proposal:
when version gets deleted, create new entry in history as:
<org>/<app>/0.0.1-dev | deleted version 0.0.2-dev
(proposal 1) or<org>/<app>/0.0.1-dev | deleted version 0.0.2-dev (now at 0.0.1-dev)
(proposal 2)The text was updated successfully, but these errors were encountered: