-
Notifications
You must be signed in to change notification settings - Fork 203
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
Chore/consistent type hints #122
Conversation
…orking in the toml file for some reason)
…accept series and dfs as input, always returns a series though! Change needed for Asset
…commit fixes that.
…s are used correctly
3f20d69
to
968afc2
Compare
968afc2
to
1c61a22
Compare
@PietropaoloFrisoni This is finally ready to be merged. Important NotePlease, do not review this thoroughly. I only assigned this PR to you, so that you can have a quick look at some of the changes I point out to you. Please ignore everything else, it is just too much to review. :) I also left you a message on slack. |
Congrats man! This is quite a careful and thorough work. it certainly brings |
Using type hints throughout FinQuant and introducing type checks in functions/methods that raise appropriate error messages if an argument is of an unexpected type.
This commit also introduces custom data types, e.g.
FLOAT
asUnion[np.floating, float]
and more to simplify type hints. Moreover, type validation is now done with a new module/functiontype_validation
that also simplifies type validations.Finally, the documentation for all modules in
finquant
has been updated.This closes #94 and also closes #118.