-
Notifications
You must be signed in to change notification settings - Fork 893
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Casing Consistency: Rename TensorFlowModelDataset to ...DataSet #2494
Comments
@BrianCechmanek Great catch! It's not intentional (AFAIK), just an oversight. :) You're welcome to make a PR, but please do so on https://github.com/kedro-org/kedro-plugins instead (the new home from datasets). |
It would also be nice to make everything |
Tubular!
|
I don't think it's necessary for datasets, but let me confirm... |
See #2129 |
Thanks @astrojuanlu - sorry I missed that. Sounds like that's a much bigger task (and probably above my head). I think this can be safely closed, then. |
@BrianCechmanek I think it may be fine to go ahead with this, since the massive change will probably have to wait until 0.19 release, while this could help improve consistency in the shorter term. But maybe we can just wait for a confirmation on this; don't want you to do work unnecessarily. :) |
Description
TensorFlowModelDataset
is the only included dataset not following the "DataSet" casing consistency.Context
Maintaining consistency assists with mental overhead.
Possible Implementation
I believe the fix is just a refactor in the 7 instances across the following two files:
./extras/datasets/tensorflow/tensorflow_model_dataset.py
./extras/datasets/tensorflow/__init__.py:__all__
I am happy to submit a PR of the refactor, if appropriate.
Possible Alternatives
It may have been intentional to break convention for this DataSet. Searching open and closed Issues, I found no reference.
NB : I believe I followed the contributing guide correctly. Please let me know if not - first ever OS Issue submission :)
The text was updated successfully, but these errors were encountered: