Closed pierrotsmnrd closed 2 years ago
PR #79
I've tested the PR, thanks a lot for the great work ! I've noticed some improvements that I think belong in this PR :
channel:[]
in the yaml editor. Simply remove the line. Because channel:[]
is not valid YAML for an env descriptionchannel
line. When I switch back to the yaml composer, I get a blank page. It should just show the channel
section empty.requested packages
section should be unfolded (even if empty), that's often where the users will go first.requested packages
section, switched to the yaml editor, and switched back to the yaml composer. The requested packages
was folded again. as for the previous point, keep this section open all the time. Also, if possible, keep it scrolled at the same position it was after having switching back from the yaml editor.requested packages
section, hide the installed version
column. right now it's showing the selected version (see screenshot below), which it shouldn't. Simply hide the whole column when creating.installed version
column doesn't appear. We mentioned hiding this column before and I might have been unclear on when to hide or show it :) edit
: it triggered a new build. It should only update the description. Screenshot for point 6 with the installed version
appearing and showing selected version
number, whereas it should be simply be hidden.
Second PR ready for review : #86
Goal :
Allowing the user to create a new environment, in a given namespace
Design :
Behavior :
Clicking on the
+
button at the right of a namespace, opens a new empty tab to create a new env in that namespacethe field to enter the new env name has a placeholder text "Environment name"
The field to enter the description is shown as a multiline text box, the other usual components (Build, Status ...) are hidden
The Specification box only contains the "Requested packages" and "Channels" boxes
Clicking on
Create
will call the API to create the env, and update the UI to display the env as a classic, read-only modeClicking on the switch "Switch to YAML Editor" will turn the UI into :
the YAML editor we chose is : https://www.npmjs.com/package/@uiw/react-codemirror
In case of error when creating the env, the error message returned by the API will be shown like this :
API and data
POST /conda-store/api/v1/specification/
specification
andnamespace
namespace
is the name of the namespace in which adding the envspecification
is the YAML representing the env, with its newline characters replaced by "\n". example : if YAML is :Other :
Split this main component into sub-components as necessary.