Rust SDK #436
Rust SDK #436
Conversation
Fix Licence Name in cargo.toml and Indentation in the twig templates
+ Allow package name to be changed in the sdk-generator for rust
…Onic/sdk-generator into rust-language-support
+ Added Example Generation + Changed example in README.md to use variable package name
Added first implementation of Exceptions into the Rust SDK
Co-authored-by: Damodar Lohani <[email protected]>
Co-authored-by: Damodar Lohani <[email protected]>
Add add_self_signed function to Client in SDK and Remove Cookies
wess
left a comment
wess
left a comment
There was a problem hiding this comment.
Only suggestion is working on reducing clone (which we have already talked about). Thanks for this!
|
Love to see it. I was thinking of creating a Rust SDK however I have no experience with it and it's a lot of work. Thank you for all that you have done |
|
Note: All Rust tests are passing in above commit, non-rust tests are failing. |
|
How is this going? Would love to see a Rust SDK for server-side ;) |
|
|
||
|  | ||
|  | ||
| {% if sdk.warning %} |
There was a problem hiding this comment.
would be nice if these if/endif blocks could be consistent with whitespace. I prefer:
{if}
thing..
{endif}```
without the whitespace between if & thing.
|
@PineappleIOnic any news on this? Can I help out in any way? |
|
@PineappleIOnic is this branch dead? Seems like PR was never reviewed |
|
@LcsH0s Yeah unfortunately this branch is currently dead, it is very old and Rust, Appwrite and the ways we generate SDK's have changed quite drastically, so we'll need to possibly rewrite this from the ground up |
|
@PineappleIOnic thank you for all the work you did at least |
7 participants
This PR has Template files and Tests for an Appwrite Rust SDK,
I have also written the foobar tests and ran them myself to confirm that this SDK works correctly, This SDK Conforms as closely as it can with the Rust Language's Standards so it shouldn't compile with any warnings apart from unused imports which can't be avoided due to how the templates work.
Currently, the API is blocking I/O but I plan to add async support in the future behind a feature in the crate which I'm quite excited to do considering I'm not very good with async rust.
This PR also has full compatibility with Appwrite's response models making it as easy as possible for users to use the SDK. A Playground has already been written and tested and a PR is being prepared.