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
I think that config'd metadata fields would be cool, essentially it would be a toml table in the config file with keys indicating the md keys and values indicating the types, with some special handling for "enum-like" values.
e.g. the current default config would look like (exact type strings may vary):
this would mean that list is configurable on a per-table basis (including order) and that tables can decide on what md they want for that session.
Alternatively we could allow arbitrary metadata, but ui for that gets complex pretty quick and would like to encourage adding md so make it as easy as possible.
The text was updated successfully, but these errors were encountered:
ksunden
added a commit
to ksunden/bluesky-cmds
that referenced
this issue
Jun 28, 2022
Tides us over until wright-group#19 is properly implemented
Just adds a lot of names to the combo and sorts them.
Additionally an "unspecified" option is available, and is the default
Tides us over until #19 is properly implemented
Just adds a lot of names to the combo and sorts them.
Additionally an "unspecified" option is available, and is the default
I think that config'd metadata fields would be cool, essentially it would be a toml table in the config file with keys indicating the md keys and values indicating the types, with some special handling for "enum-like" values.
e.g. the current default config would look like (exact type strings may vary):
this would mean that list is configurable on a per-table basis (including order) and that tables can decide on what md they want for that session.
Alternatively we could allow arbitrary metadata, but ui for that gets complex pretty quick and would like to encourage adding md so make it as easy as possible.
The text was updated successfully, but these errors were encountered: