Create environment : full feature

[pierrotsmnrd]

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 namespace

• the 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

  • The "Requested packages" doesn't show column "installed version".
  • The list of requested packages should be empty, the screenshot shows Python 3.8 only for example purpose
  • The list of channels must be empty, the screenshot shows conda-forge only for example purpose

• Clicking on Create will call the API to create the env, and update the UI to display the env as a classic, read-only mode

• Clicking on the switch "Switch to YAML Editor" will turn the UI into :

  • "Switch to YAML Editor" becomes "Switch to standard view"
  • the shown YAML text must reflect what the user entered in the standard view (same channels and packages), and any modification in the YAML must be applied to the standard view when the user switches back.

• 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

• the API endpoint to use is POST /conda-store/api/v1/specification/
• It takes as a body a JSON dict with two keys, specification and namespace
  • namespace is the name of the namespace in which adding the env
  • specification is the YAML representing the env, with its newline characters replaced by "\n". example : if YAML is :

    
    channels:

• conda-forge dependencies:
• python ==3.9
• flask
• pandas
• pip:
  • nothing
• ipykernel description: test description name: python-flask-env-test prefix: null

  the expected JSON to add this env to a namespace named "test-api" is : 
  ```json
  {
  "specification": "channels:\n- conda-forge\ndependencies:\n- python ==3.9\n- flask\n- pandas\n- pip:\n  - nothing\n- ipykernel\ndescription: test description\nname: python-flask-env-test\nprefix: null",
  "namespace": "test-api"
  }

Other :

Split this main component into sub-components as necessary.

[pierrotsmnrd]

PR #79

[pierrotsmnrd]

I've tested the PR, thanks a lot for the great work ! I've noticed some improvements that I think belong in this PR :

• [x] 1. if there are no added channels in the yaml composer, don't show channel:[] in the yaml editor. Simply remove the line. Because channel:[] is not valid YAML for an env description
• [x] 2. I've switched to the yaml editor and removed the channel line. When I switch back to the yaml composer, I get a blank page. It should just show the channel section empty.
• [x] 3. When creating or editing a channel, the requested packages section should be unfolded (even if empty), that's often where the users will go first.
• [x] 4. I had unfolded the 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.
• [x] 5. The notification when the env is being created is very good looking ! Once the user has clicked on create, and before the notification appears, switch the whole view to read-only mode to leave the edition mode and refresh the list of envs and namespaces to let it appear.
• [x] 6. When creating an env, in the 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.
• [x] 7. Once I go back to the read-only view, the 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 :)
• [ ] 8. I've edited the description of an env, not the packages, and clicked edit : it triggered a new build. It should only update the description.
• [x] 9. Add a cancel button to switch back from edit to read-only mode.

Screenshot for point 6 with the installed version appearing and showing selected version number, whereas it should be simply be hidden.

[pierrotsmnrd]

Second PR ready for review : #86