-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
馃殌 Feature: Export Typescript interfaces for collections #5441
Comments
Can I try to work on this issue? |
@HannesPaa this is a nice idea, It would be beneficial to have this support not just for typescript but also for other languages and frameworks like java, kotlin, dart etc. |
Sure @Vishrut19 go for it |
FYI we are working on a typescript abstraction layer for all appwrite configuration, which serves as a reference base (appwrite.json much more accomplished) with automatic typing, base schema update, tsx export, etc... It is currently used for our internal needs, we are optimizing it and in a few months we will probably make it available |
So, should I work on this issue or not? |
This feature should be implemented as soon as possible |
Good to know @fliitor , how is it going now with the the layer? |
Also @Vishrut19 , this issue was assigned to you to work on, please let us know any updates : ) |
Can someone suggest me where I need to make changes, like in which file or in which folder should I look for? @joeyouss if possible please help |
We abandoned the idea of making it accessible because the code had become too specific to our needs. However, it is possible to use codegen to generate tsx from graphql |
馃敄 Feature description
For each collection there is a button to download a typescript interface not just with the normal "Document Object" Types, but with all attributes.
For example:
or
馃帳 Pitch
The benefits of Typescript are obviously great, especially when working with data.
When i want to work with data from Appwrite i must be sure that i don't mix up types, so i often make my own interfaces. This feature would save some work and make sure that there are no errors in the interfaces.
馃憖 Have you spent some time to check if this issue has been raised before?
馃彚 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: