graphql-python / graphql-python/flask-graphql
Separate endpoint for GraphiQL
- Linguagem predominante
- Python
- Estrelas
- 1.3k
- Forks
- 139
- Métricas de merge de PRs
- Nenhum PR com merge em 30d
Descrição
Hi,
wouldn't it make sense to have separate endpoints for GraphQL and GraphiQL? As per [README](https://github.com/graphql-python/flask-graphql#usage), there should be two endpoints (`/graphql` and `/graphiql`), however only `/graphql` gets exposed. Let's say I would like to publish GraphiQL only to selected group of people (e.g. frontend developers) and protect it by authentication. Having a separate endpoint would make whole thing much easier.
Guia de contribuição
Nenhum guia de contribuição indexado para este repositório
Direção de pesquisa
Start with the README usage section to compare the documented /graphql and /graphiql endpoints, then trace where the current single endpoint is configured in the Flask integration. Done means GraphQL and GraphiQL can be exposed separately, with GraphiQL independently protected or restricted as requested.
Escrita pelo modelo de indexação a partir do texto da issue.
Avaliação
- Stack de tecnologia
- flask, graphql, python
- Domínio
- api, backend
- Tipo de issue
- Funcionalidade
- Dificuldade
- 3/5
- Tempo estimado
- 1-2 dias
- Status de atividade
- Estagnada
- Clareza
- Razoavelmente clara
- Facilidade para iniciantes
- 35/100