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

devfile v1 -> v2 convertion enchancements #21103

Closed
9 of 10 tasks
ibuziuk opened this issue Feb 1, 2022 · 3 comments
Closed
9 of 10 tasks

devfile v1 -> v2 convertion enchancements #21103

ibuziuk opened this issue Feb 1, 2022 · 3 comments
Assignees
Labels
area/dashboard kind/enhancement A feature request - must adhere to the feature request template. severity/P1 Has a major impact to usage or development of the system. sprint/current

Comments

@ibuziuk
Copy link
Member

ibuziuk commented Feb 1, 2022

Is your enhancement related to a problem? Please describe

UX / Docs

  • Action dropdown should not exist since there is only one action / if the only action is delete, lets make it a button /

image

  • Once the conversion is done successfully "Convert" button shd gone away, There shd not be a button and then a error message (The conversion button should not be active the second time but we should show the delete)
  • Documentation must be clear as to what is the difference between devfile1 Vs devfle2 and what changes will the user see
    - N.B. There is a separate issue for documentation Provide FAQ / Known issues / Troubleshooting for devfile v1 -> devfile v2 convertion #21005 (TODO discuss on cabal)
    - Specify clearly what possible error messages can happen and what they need to do on CRW (?) docs (TODO discuss on cabal)
    - [ ] Add FAQ / Known issues with volumes to devfile.io / update the link from UD to FAQ (action prepare content)
  • Can we find a way to warn if they will succeed in conversion? and warn them upfront. (TODO discuss on cabal) (cover as part of docs FAQ / Known issues)
  • In the warning you should specify that it’s possible to convert it automatically with the button above. (Convert, than look to FAQ if is failing) fix: Improving the deprecation note che-dashboard#457

Features:

Bugs

Describe the solution you'd like

N/A

Describe alternatives you've considered

No response

Additional context

The initial convention mechanism has been implemented as part of #20845

@ibuziuk ibuziuk added kind/enhancement A feature request - must adhere to the feature request template. area/dashboard sprint/next labels Feb 1, 2022
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Feb 1, 2022
@ibuziuk ibuziuk added severity/P1 Has a major impact to usage or development of the system. and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Feb 1, 2022
@ibuziuk ibuziuk mentioned this issue Feb 1, 2022
35 tasks
@akurinnoy akurinnoy self-assigned this Feb 7, 2022
@ibuziuk
Copy link
Member Author

ibuziuk commented Feb 8, 2022

@l0rd updated deprecated note PR - eclipse-che/che-dashboard#457

@ibuziuk
Copy link
Member Author

ibuziuk commented Feb 10, 2022

@akurinnoy could you please also address annotation creation as part of enhancements #21153

@ibuziuk
Copy link
Member Author

ibuziuk commented Feb 22, 2022

Closing the issue since we have 2 separate tickets for docs and the conversion enhancements:

@ibuziuk ibuziuk closed this as completed Feb 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/dashboard kind/enhancement A feature request - must adhere to the feature request template. severity/P1 Has a major impact to usage or development of the system. sprint/current
Projects
None yet
Development

No branches or pull requests

3 participants