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
Is your feature request related to a problem? Please describe.
Currently, some datasets have a configuration, while others don't. It would be simpler for the user to always have configuration names to refer to
Describe the solution you'd like
In that sense inspect.get_dataset_config_names should always return at least one configuration name, be it default or Check___region_1 (for community datasets like Check/region_1).
severo
changed the title
Make inspect.get_dataset_config_names always return a nen-empty list of configs
Make inspect.get_dataset_config_names always return a non-empty list of configs
Oct 22, 2021
Hi @severo, I guess this issue requests not only to be able to access the configuration name (by using inspect.get_dataset_config_names), but the configuration itself as well (I mean you use the name to get the configuration afterwards, maybe using builder_cls.builder_configs), is this right?
Yes, maybe the issue could be reformulated. As a user, I want to avoid having to manage special cases:
I want to be able to get the names of a dataset's configs, and use them in the rest of the API (get the data, get the split names, etc).
I don't want to have to manage datasets with named configs (glue) differently from datasets without named configs (acronym_identification, Check/region_1)
Is your feature request related to a problem? Please describe.
Currently, some datasets have a configuration, while others don't. It would be simpler for the user to always have configuration names to refer to
Describe the solution you'd like
In that sense inspect.get_dataset_config_names should always return at least one configuration name, be it
default
orCheck___region_1
(for community datasets likeCheck/region_1
).datasets/src/datasets/inspect.py
Line 161 in c5747a5
The text was updated successfully, but these errors were encountered: