Open GeekArthur opened 4 years ago
/tech-topic
From tech topics:
We need the API to support allowing each extension to return multiple templates and tagging each of them as strong or weak (or some similar mechanism).
When merged together, the API is going to return some number of strong and weak options. This leads to several cases:
We need to have a walkthrough with Guy (design) about path A (e.g. it's not obvious that No button goes to the fallback list today), path B (do we still put up a dialog first?), and general concerns (e.g. the list of options is still filtered - how do we show the full list, or in the extreme case even get you back to the Manage Templates page?)
For Appsody & odo we don't have enough information to correctly filter the list of templates, i.e. the weak list is currently all templates. The suggestion is to start by using some basic matching or heuristics (e.g. if title or description contains the name of the project's language).
Get some feedbacks from @deboer-tim in odo extension bind case demo, so create this issue for tech topic.
Background: Currently we have two generic cases for all project types (Codewind, odo, Appsody) bind:
Bind vanilla project / project without strong indicator: We won't detect the project type automatically and give the user options as the screenshot shown below
Bind project with strong indicator: We can detect the project type and give the user options as the screenshot shown below
Topics:
.appsody-config.yaml
) and odo (.odo
), probably we can provide strong indicator for Codewind as well by usingDockerfile
given both odo and Appsody don't haveDockerfile
For bind project without strong indicator: should we still use the existing design which is always let user confirm if the project is correct if we can't detect the project type via strong indicator?
Potential proposals: