Did you search for existing issues already?
Jah
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Switching between different collection files is cumbersome. This leads to joining collection files that conceptually make more sense to be separate (e.g. multiple different APIs under the same collection. A subsequent effect of this is ending up with profiles that represent different things, e.g. ("API A Profile 1", "API A Profile 2", "API B Profile 1", "API B Profile 2").
Describe the solution you'd like
A clear and concise description of what you want to happen
A feature in the TUI (e.g. modal) to switch between different collections. The modal would be populated by the list of known collections in the DB.
An additional helper for this would be to support an optional name field in the root of a collection file. The modal could include a second Name column for each collection in addition to its path, allowing the user to provide a friendly name.
Modal would need a footnote explaining which collections are visible and how to open a collection for the first time. Could include an additional option in the list to enter a path manually; may not be worth it though since this would only be useful for first-time openings and the same can be achieved by just running slumber -f ...
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered
- Switching between collections manually (current state)
- Identifying collection files by searching the file system instead of using the DB
- Would require a rule such as "collection files must end with
.slumber.yml", and wouldn't find collections outside the working tree
Additional context
Add any other context or screenshots about the feature request here
Did you search for existing issues already?
Jah
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Switching between different collection files is cumbersome. This leads to joining collection files that conceptually make more sense to be separate (e.g. multiple different APIs under the same collection. A subsequent effect of this is ending up with profiles that represent different things, e.g. ("API A Profile 1", "API A Profile 2", "API B Profile 1", "API B Profile 2").
Describe the solution you'd like
A clear and concise description of what you want to happen
A feature in the TUI (e.g. modal) to switch between different collections. The modal would be populated by the list of known collections in the DB.
An additional helper for this would be to support an optional
namefield in the root of a collection file. The modal could include a secondNamecolumn for each collection in addition to its path, allowing the user to provide a friendly name.Modal would need a footnote explaining which collections are visible and how to open a collection for the first time. Could include an additional option in the list to enter a path manually; may not be worth it though since this would only be useful for first-time openings and the same can be achieved by just running
slumber -f ...Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered
.slumber.yml", and wouldn't find collections outside the working treeAdditional context
Add any other context or screenshots about the feature request here