Skip to content

add edit sub-commad #541

Description

@plastikfan

We can aid the user in their quest to edit config files. Instead of putting the burden on the user to know exactly the location of the config files, we can provide a new edit sub-command, that abstracts this part of it away.

Can use the $EDITOR value to launch the user controlled editor. There are mutiple file that can be edited, but we don't want to force the user to know exactly the full path to the file. We should use the value of JAY environment variables such as $JAY_CONFIG_DIR and $JAY_THEMES_DIR to access files. We create an enumeration representing the files tyhat can be edited eg:

  • application-config (jay.yml): app
  • ui config (jay.ui.yml): ui
  • themes config (see note below 📕): themes

etc...

This may be complicated by the fact that various different formats may be used, so will and to develop a flexible resolution process.

The command could be launched as:

jay edit app

📕 Themes: this is a little more complicated because a user can have many themes in their folder, which can be called upon using the --theme flag. So we could use a bubbletea file picker user interface and allow the user to select from the list of files available.

Metadata

Metadata

Assignees

Labels

featureNew feature or request

Fields

No fields configured for Feature.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions