-
Notifications
You must be signed in to change notification settings - Fork 18
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
v1.0.0-alpha #188
v1.0.0-alpha #188
Conversation
- changed organisation and package name - updated maintainers - removed previous code items - updated tools Signed-off-by: Jean-Baptiste Bianchi <[email protected]>
Signed-off-by: Jean-Baptiste Bianchi <[email protected]>
Signed-off-by: Jean-Baptiste Bianchi <[email protected]>
Signed-off-by: Jean-Baptiste Bianchi <[email protected]>
Signed-off-by: Jean-Baptiste Bianchi <[email protected]>
Signed-off-by: Jean-Baptiste Bianchi <[email protected]>
Signed-off-by: Jean-Baptiste Bianchi <[email protected]>
Signed-off-by: Jean-Baptiste Bianchi <[email protected]>
Signed-off-by: Jean-Baptiste Bianchi <[email protected]>
Signed-off-by: Jean-Baptiste Bianchi <[email protected]>
Signed-off-by: Jean-Baptiste Bianchi <[email protected]>
I think the branch reached a mature enough state for code review. The README has been updated to match the new API and I added a Tooling Architecture document to describe how the SDK is built. Any input or help is welcome ❤️ |
Signed-off-by: Jean-Baptiste Bianchi <[email protected]>
Signed-off-by: Jean-Baptiste Bianchi <[email protected]>
Prevents accessing a property which is declared in one type but not the other: ``` type A = { p: string; }; type B = { k: number; }; const foo = {} as A | B; foo.p = "bar"; //>Property 'p' does not exist on type 'A | B'. //> Property 'p' does not exist on type 'B'. ``` Signed-off-by: Jean-Baptiste Bianchi <[email protected]>
…t in the tooling Signed-off-by: Jean-Baptiste Bianchi <[email protected]>
Signed-off-by: Jean-Baptiste Bianchi <[email protected]>
e7e49d5
to
6c040e0
Compare
Signed-off-by: Jean-Baptiste Bianchi <[email protected]>
6c040e0
to
fe3bbee
Compare
Signed-off-by: Jean-Baptiste Bianchi <[email protected]>
Allows to validate an item against the workflow, for instance a transition, the use of a a function, ... Signed-off-by: Jean-Baptiste Bianchi <[email protected]>
Signed-off-by: Jean-Baptiste Bianchi <[email protected]>
Signed-off-by: Jean-Baptiste Bianchi <[email protected]>
Signed-off-by: Jean-Baptiste Bianchi <[email protected]>
Hello. Is there any plan to merge it and have a newer version of the TS SDK released supporting spec version |
@chakrabar Thank you for your interest! Yes, there are plans to move forward, but we don't have a definitive timeline at the moment. Ideally, we’d like to enhance the unit tests and add some examples to ensure a solid foundation. I'll do my best to make progress in the coming days, depending on my availability. In the meantime, please feel free to contribute if you'd like to tackle any tasks—we’d greatly appreciate your help! |
- Readded browser and node examples - Added call async api/grpc/function tests Signed-off-by: Jean-Baptiste Bianchi <[email protected]>
- Fixed the builders output type - Added more samples Signed-off-by: Jean-Baptiste Bianchi <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great to me! Cheers ❤️
Many thanks for submitting your Pull Request ❤️!
What this PR does / why we need it:
Support for v1.0.0-alpha (#186)
Special notes for reviewers:
Type generation for schema is very unstable, a small change in the spec can have a big impact on the generated types and underlying validators, classes and builders.
Classes are empty. It's just a trick to maybe have some kind of runtime type checking (see builders tests).
Additional information (if needed):
Currently uses a manually modified version of the spec's JSON Schema. Yield completely different results otherwise.