Skip to content
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

Insert GraphQL snippets from api-examples on other pages #455

Closed
Mythicaeda opened this issue Nov 10, 2022 · 0 comments · Fixed by #456
Closed

Insert GraphQL snippets from api-examples on other pages #455

Mythicaeda opened this issue Nov 10, 2022 · 0 comments · Fixed by #456
Assignees
Labels
documentation Improvements or additions to documentation refactor A code change that neither fixes a bug nor adds a feature

Comments

@Mythicaeda
Copy link
Contributor

Currently in our docs, when we want to have a GraphQL query/mutation present in both api-examples and on a specific documentation page, we write the query/mutation twice, once in both spot. We ought to instead have all of those queries only exist in api-examples, and dynamically insert them into the specific documentation page.

@Mythicaeda Mythicaeda added documentation Improvements or additions to documentation refactor A code change that neither fixes a bug nor adds a feature labels Nov 10, 2022
@Mythicaeda Mythicaeda added this to the 1.1.0 milestone Nov 10, 2022
@Mythicaeda Mythicaeda self-assigned this Nov 10, 2022
@Mythicaeda Mythicaeda added this to Aerie Nov 10, 2022
@Mythicaeda Mythicaeda moved this to In Review in Aerie Nov 10, 2022
This was referenced Nov 10, 2022
Repository owner moved this from In Review to Done in Aerie Nov 10, 2022
@camargo camargo modified the milestones: 1.1.0, 1.1.0 - Documentation Updates Nov 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation refactor A code change that neither fixes a bug nor adds a feature
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants