Sequence Editor Follow - Part 2

[duranb]

The following are the remaining Sequence Editor tasks after #1291

Tasks

Preview Give feedback

1. SelectedCommand panel needs to be updated to have consistent styling #1394
   +0
2. Adding a boolean enum command (i.e. C FSW_CMD_0...) yields an incorrect selected command view #1395
   bug sequencing +2
   
3. Expansion/Parcel/Sequence update queries should be combined into one
4. SelectedCommand.svelte - address TODOs
5. Add unit tests for all the new utility TS files under /codemirror and /new-sequence-editor
6. Is it necessary to keep logger.ts? Shouldn't those errors/messages be more exposed?
7. Address any TODOs in /new-sequence-editor if addressable
8. SearchableDropdown.svelte - @joswig I think that displaying a message somewhere on the list (bottom maybe?) would be necessary if the list is truncated to avoid confusion
9. Discuss why the sequence editor has its own branding
10. Move the new dependencies from devDependencies to dependencies in package.json
11. Uploading an invalid file type results in a silent failure on Dictionary form
12. Add tests for adding / removing dictionaries to parcels
13. Sequence form "*Editor" components should dispatch an event rather than invoke a callback setInEditor #1540
    sequencing +1
14. Selected Command Support for Library Sequences #1550
    feature sequencing +2
    

Optional Tasks

Preview Give feedback

1. More comments in functions with long and deeply nested conditional statements like commandLinter