-
Notifications
You must be signed in to change notification settings - Fork 141
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
[ENH] Type hints for primitives and string arguments #1454
Comments
Hello, I would like to start on this issue. I am taking up "aeon.classification.distance_based._time_series_neighbors.py" script to start with. |
@all-contributors please add @nileenagp for Code |
I've put up a pull request to add @nileenagp! 🎉 |
Hello, |
No, if the dependency is optional it should not be imported at the top level of a file. This would exclude it from specific type hints like that I imagine. |
Thanks for the confirmation, I will leave that type hint for now. |
Hello @TonyBagnall , is this issue still open to work on ? Thank you! |
Hi @YashviMehta03, this one is a bit too big for a single person really. I would post here selecting a part of the package you want to add type hints too and go from there. |
Hello @MatthewMiddlehurst , yes right.
I would like to work on it , could you assign it? |
Describe the feature or idea you want to propose
we would like to increase the use of type hints, and a good first issue is to add them for the simplest case when arguments are primitives (int, float, bool) or strings. Pick a package, look through the code and add type hints. Just for primitives for now, more complex types need a bit of thought. Many have npt.ArrayLike types, but we have not decided on standardising on that, so leave these alone. Dont feel you have to do them all, this is a good first issue to get you started.
Describe your proposed solution
for example, the constructor for the anomaly detection algorithm STRAY has these type hints
but the segmentation algorithm CLASP does not
Describe alternatives you've considered, if relevant
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: