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
To simultaneously be more specific (because there are other .csv paths) and be more general (because a dataset may not always be a .csv)
Probably not a good idea to heavily overload the semantics of this argument--e.g. by allowing dataset_path to be any of 12 different things--but it repeatedly annoys me that the name csv_path is not very clear from context.
Maybe dataset_csv_path? But that's starting to get pretty verbose
The text was updated successfully, but these errors were encountered:
because `csv_path` is not very specific, and because
the path to a dataset may not always be
the path to a csv (although it is for now)
- Rename `csv_path` -> `dataset_path` in vak/config
- Rename `csv_path` -> `dataset_path` in vak/core
- Rename `csv_path` -> `dataset_path` in vak/cli
- Rename `csv_path` -> `dataset_path` in tests
because `csv_path` is not very specific, and because
the path to a dataset may not always be
the path to a csv (although it is for now)
- Rename `csv_path` -> `dataset_path` in vak/config
- Rename `csv_path` -> `dataset_path` in vak/core
- Rename `csv_path` -> `dataset_path` in vak/cli
- Rename `csv_path` -> `dataset_path` in tests
To simultaneously be more specific (because there are other .csv paths) and be more general (because a dataset may not always be a .csv)
Probably not a good idea to heavily overload the semantics of this argument--e.g. by allowing
dataset_path
to be any of 12 different things--but it repeatedly annoys me that the namecsv_path
is not very clear from context.Maybe
dataset_csv_path
? But that's starting to get pretty verboseThe text was updated successfully, but these errors were encountered: