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
How to go for a flask-admin "kind of" interface? #260
Comments
#167 provided some ideas on this topic. |
Thanks! |
Yeah I was actually trying to do that too, with iView Admin, for company projects. The login API barely worked, and I didn't find time to continue yet. Graphene was planned, but it was too much to include at a time. |
don't know if it helps, but aiohttp_admin uses |
@gyermolenko looks interesting! ..and familiar 😈 |
@gyermolenko and @fantix: thanks for the inputs. This currently leaves us with a lot of choices in the architecture: rest vs graphQL, sanic vs aiohttp, react vs angular... emacs vs vi ;) I think i'll try some options, and hopefully give some feedbacks. |
Just a quick update (i've been diverted to many other works, and also a switch from sanic to aiohttp). I started learning and experimenting with GraphQL, and grabbed the structure of graphene-sqlalchemy to create a graphene-gino package. Nothing that i can publish now, just a basic working proof of concept. |
@gyermolenko https://github.com/marmelab/admin-on-rest is archived, any update on where is going forward https://github.com/aio-libs/aiohttp_admin ? |
@aprilmay what is the rational for using graphql instead of REST. Can you (quickly) explain how you made your choice? |
First, Graphql has metadata capabilities (schema description), which allows higher level operations (eg. relationships, types, caching) without too much hassle. Compared to Django admin where the logic is mostly server side, i find Graphql more appropriate with modern web applications (Angular, React, etc). So, it sounds like a reasonable choice compared to plain REST for starting such a project as of today. @amirouche: are you planning to work on it? |
@aprilmay I am investigating the use of GINO / aiohttp for a new project and stumbled upon this conversation. I very keen to build "my own castles in the sky" (ref) so take what I say with a grain of salt.
I don't buy popularity by default.
See this example extracted from the official apollo getting started: const Feed = () => (
<Query query={GET_DOGS}>
{({ loading, error, data }) => {
if (error) return <Error />
if (loading || !data) return <Fetching />;
return <DogList dogs={data.dogs} />
}}
</Query>
) See the second
If it's not an error and it's not loading then why there is no
I agree.
Mind the fact that GraphQL is around for almost as much time as ReactJS and did not gain as much adoption. I like the idea of GraphQL as standard way to query the backend but I think it is missing some bits. As of yet, with GraphQL, I don't know:
IMHO it only looks reasonable. From a marketing point of view, I see that it will be possible to sell that experience. From an engineering point of view, I am not buying... yet! |
Very valid points. Don't buy anything from me either ;) I can give some information, from my experience with a prototype (Angular/Apollo and Aiohttp/Gino):
|
I saw this project recently: Maybe it can be mentioned in the docs. |
It's a very generic question, so i leave it open for comments and suggestions.
Many web frameworks propose a customizable "admin" interface, eg. Flask-admin, Django admin, etc.
So, with a typical Sanic/Gino tool stack, what options do we have for such a facility?
The text was updated successfully, but these errors were encountered: