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

[Parent Issue] Mutation Documentation #360

Closed
sumitra19jha opened this issue Nov 10, 2021 · 6 comments
Closed

[Parent Issue] Mutation Documentation #360

sumitra19jha opened this issue Nov 10, 2021 · 6 comments
Labels
documentation Improvements or additions to documentation good first issue Good for newcomers no-issue-activity No issue activity parent Parent issue

Comments

@sumitra19jha
Copy link
Contributor

Is your feature request related to a problem? Please describe.
Graph API's Mutation documentation needs to be added for a better understanding

Describe the solution you'd like
While writing the documentation make sure of the following points:

  1. Aim of the mutation
  2. Describe input fields
  3. Describe return types
  4. If a mutation is causing changes at different data fields in the database which is not part of the return type, then state and describe those too. For this, you need to go through the API Code.

Additional context
As there are large number of mutations, so before documentation please specify which mutation you are working on so that others can work accordingly.

@github-actions github-actions bot added documentation Improvements or additions to documentation unapproved Unapproved for Pull Request labels Nov 10, 2021
@sumitra19jha sumitra19jha added parent Parent issue good first issue Good for newcomers and removed unapproved Unapproved for Pull Request labels Nov 23, 2021
@Rottenblasters
Copy link

@sumitra19jha I would like to work on this. I am new to the organization so can you guide me where to write the documentation?

@palisadoes
Copy link
Contributor

@sumitra19jha Where are the child issues related to this issue?

@PSY27
Copy link

PSY27 commented Dec 18, 2021

Hello can i work on this

@akshatgarg12
Copy link
Contributor

I would like to work on this, specifically organisation mutations, should i create a child issue for this?

@palisadoes
Copy link
Contributor

palisadoes commented Feb 10, 2022

@akshatgarg12 One of our mentors is working on a way to automate this, possibly using Swagger UI. His name is Xavier Bryson and is based in Jamaica. You can contact him on slack.

Please contact him. He could need assistance.

@github-actions
Copy link

This issue did not get any activity in the past 60 days and will be closed in 365 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue.

@github-actions github-actions bot added the no-issue-activity No issue activity label Apr 12, 2022
@SiddheshKukade SiddheshKukade closed this as not planned Won't fix, can't repro, duplicate, stale Dec 3, 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 good first issue Good for newcomers no-issue-activity No issue activity parent Parent issue
Projects
None yet
Development

No branches or pull requests

6 participants