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
Higher level api that abstracts away FastAPI #305
Comments
/api
for page urls
All sounds good but AFAIK FastUI aims to be a framework (most probably language) agnostic tool. Quoting README.md:
Depending on the README, I could say that "your request is irrelevant". PS: I don't think encapsulating FastAPI is not a good idea. It doesn't bring anything to the table, except reducing imports to one or maybe two lines. |
@hasansezertasan good point! |
Maybe it's just me, but I think it would be nice if FastUI also had a slightly higher level of abstraction that encapsulates FastAPI, for cases where one does not want/need to work directly with FastAPI.
Here's what I'm thinking...
Right now, I have to do this:
What I'd love to be able to do is something like this:
When I have a lot of different pages, the simplified api would be DRY'er.
The text was updated successfully, but these errors were encountered: