-
Notifications
You must be signed in to change notification settings - Fork 697
[FEAT] : Motia Python Types #665
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
base: main
Are you sure you want to change the base?
Conversation
@riturajFi is attempting to deploy a commit to the motia Team on Vercel. A member of the Team first needs to authorize it. |
2cc67e3
to
ef637c1
Compare
@sergiofilhowz would like your review on the PR regarding functionality, code quality, edge cases etc on this PR. |
Hey @riturajFi, Thanks for your contribution - This is big! Team is going to review this as soon as possible, currently working on a big release for the cloud. |
80c38d6
to
e304aec
Compare
Hey @riturajFi, how's it going? Do you need any help here? |
Hi @rohitg00 sorry for the delay - this will be done shortly |
8757c84
to
4f08e58
Compare
0b3739d
to
a29b6df
Compare
Hi @rohitg00 would love a review of the code and approach |
a29b6df
to
f10bec2
Compare
Solves: #485
Description
This update introduces strongly typed Python definitions for:
Input Types
API request and response objects
FlowContext types across all step files
It also resolves the previous issue where nested objects were incorrectly inferred as unknown in Python type definitions.