graphql / graphql/graphql.github.io
Write more FAQ answers based on feedback
- Lenguaje dominante
- TypeScript
- Estrellas
- 889
- Forks
- 1.5k
- Merge medio
- 4 d 12 h
- PR fusionados (30 d)
- 21
Descripción
The following questions are some ideas of what questions could be added to the FAQ page based on feedback we've received on the page so far.
🙋🏼 If anyone wants to take one (or more), please comment in this issue and then [follow the contributing guidelines](https://github.com/graphql/graphql.github.io/blob/source/CONTRIBUTING.md#add-a-question-to-the-faq) to open your pull request 🚀
Here are the new questions added (sorted by section):
**Getting Started**
- [ ] Can I use GraphQL to make graphs or charts?
- [ ] What are the downsides of GraphQL?
**General**
- [ ] Does GraphQL only work with graph-like structures or data sources that are graph-based?
**Best Practices**
- [ ] Does GraphQL introduce a single point of failure?
- [ ] How can I make part of my GraphQL API private?
- [ ] How can I do error handling?
- [ ] Schema-first or code-first?
**Specification**
- [ ] Why doesn’t GraphQL have a wildcard field?
- [ ] What is the N+1 problem I keep hearing about?
Guía de contribución
Línea de trabajo
Choose one unchecked question from the issue, then read CONTRIBUTING.md at the linked “add a question to the FAQ” section before locating the FAQ page in the repository. Follow the documented contribution process, add a researched answer, and verify that the selected question is answered clearly before opening a pull request.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- graphql
- Área
- documentation
- Tipo de issue
- Documentación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Estado de actividad
- Estancado
- Claridad
- Bastante claro
- Aptitud para principiantes
- 45/100