Configurable file storage for presets

[Nokinori]

Please, make a directory with presets ~./config/saul/ configurable through flag.

[DeprecatedLuar]

I am literally working on this feature right now haha. At least I think so

I am adding now a config.toml file to every preset that can be modified via flags will be in ~/.config/saul/presets/presetname/config.toml

so you can use this saul set response --headers-only (all saul call commands affected)

or maybe saul set history --raw --body-only (all saul get response commands affected)

Lmk if you think something else

[Nokinori]

I’ve been thinking about a few ideas that could improve the experience.
The first one is the ability to choose an active "context" or "workspace". + to see all the existing workspaces in the current directory. Something like it was done here.

And the second idea is a way to configure where the workspaces are stored, ideally via a flag.
For example, being able to set a specific directory for configs, or even better just the full path to the workspace storage. So you define the path, and workspaces are automatically created there and managed accordingly. Basically, some kind of workspace storage management.

[DeprecatedLuar]

I think some of those functions already are implemented and the foundation of picking your own folder is already in place

(try saul ls/exa/dir it lists all your workspace presets)

In the roadmap I planned to add a config file and add support to flags in order to change your configs location, but I like your idea of picking specifcally where the workspaces will be

about the choose active context it has a per terminal memory management file so you can literally do this

saul pokeapi set url https://pokeapi/v1/pokemon/{?pokemon}
(pokeapi is in session memory)
saul set headers field=value (sets in pokeapi)
saul anotherapi call (switches session to anotherapi)
saul set headers field2=value2 (changes on anotherapi)

Ill have a look on the stuff you sent me more carefully in a bit, thanks for the ideas @Nokinori haha!