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
Automatically expose documented API based on the defined Operations #863
Comments
Btw Rails has an option to print all the routes, maybe that is good first start. Btw this is also about us promising to not change how routes work without it being a breaking change. |
Related to #268 |
@breadchris expressed interest in this. |
NOTE: We are now using superjson for serializing / deserializing RPC calls, so if we will be exposing them as an API, we need to look into making that work with superjson. |
From some feedback we got, this would help with allowing building mobile and other clients that can then use existing Wasp's backend. |
Btw they could create their own API by writing their own |
We could use Swagger or Openapi for this, or something similar!
It would also make sense to first work more on allowing users to define which API is public, should not change, allow them to customize it, ... , before we let them expose it like this.
The text was updated successfully, but these errors were encountered: