-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Feature request: Is there a plan to support FastAPI + SQLAlchemy for backend APIs? #2454
Comments
Yes, the same demand here |
@sanjayk-github-dev @gy15901580825 Thanks for the patience! From what I know, FastAPI and SQLAlchemy are both tools in the Python ecosystem. Wasp is a JS framework, so I'm not sure where these would fit in. There are future plans to expand this (#1074), but it's not a priority. Why do you need FastAPI and SQLAlchemy? What are you building with Wasp? |
@sodic you are right, both these tools are pretty popular in the Python ecosystem for backend API development. FastAPI provides REST API to frontend which can be easily integrated with JS framework. However I can understand if it's not a priority. |
Oh, I see. Tehcnically, there's nothing stopping you from building an API with FastAPI and connecting it to Wasp's frontend (at the end of the day, it's just React). If you need help or get stuck, ask a question in our Discord and someone from the team will help you out. |
True, that should be feasible but I feel one won't get the benefit of wasp platform unless it is a first-class citizen of the platform. |
@sanjayk-github-dev Yes, that's right. But yeah, supporting an additional runtime is a huge undertaking and not something we can do right now unfortunately. You can keep following the issue I linked above if you're interested in how this plays out :) |
No description provided.
The text was updated successfully, but these errors were encountered: