You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When new codeset is registered, it's automatically marked as "current". That seems nice because it's not necessary to provide codeset for further actions.
However it is also confusing, because e.g. 'codeset list' command will automatically use the "current" values and filter the results, so you do not see all items when you'd expect them
The text was updated successfully, but these errors were encountered:
When current codeset is saved in config file, 'codeset list' command
always uses it to filter the results. This might not be wanted, so
let's add '--all' option to ignore the filters.
Related to fuseml/fuseml#244
fuseml codeset list --help
Retrieve information about Codesets registered in FuseML
Usage:
fuseml codeset list [-p|--project PROJECT] [-l|--label LABEL] [--all] [--format {json,yaml,csv,table}] [--field COLUMN[:FIELD]]... [flags]
Flags:
--all show all codesets; ignores 'label' and 'project' options (default: false)
This is helpful I think but user has to know about it. I'm still not sure if we should do more.
Maybe we need to explicitly write the project and codeset name whenever a command is called.
(it's already there for codest list command btw)
We definitely need to add --all option to other artefacts, e.g. for workflows, otherwise default filtering would kick in
When new codeset is registered, it's automatically marked as "current". That seems nice because it's not necessary to provide codeset for further actions.
However it is also confusing, because e.g. 'codeset list' command will automatically use the "current" values and filter the results, so you do not see all items when you'd expect them
The text was updated successfully, but these errors were encountered: