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

#2 Migrate Posts ( Post Requests ) to GraphQL ( Migrate Posts API from REST to GraphQL ) #56

Closed
KristianWEB opened this issue Nov 9, 2019 · 0 comments · Fixed by #61
Assignees

Comments

@KristianWEB
Copy link
Owner

Is your feature request related to a problem? Please describe.
In this issue we are gonna be migrating creating posts functionality located in routes/posts.js.

Describe the solution you'd like
Use the resource for reference on how to migrate creating posts functionality. Just make sure you adjust that code and use it in our app ( don't straight copy/paste please! )

You will work on this feature by creating and using a branch called feature/posts-graphql-implementation

Pull Request Squashing

Please, go through these steps before you submit a PR.

  1. Make sure that your PR is not a duplicate.
  2. If not, then make sure that:

2.1. You have done your changes in a separate branch. Branches MUST have descriptive names that start with either the fix/ or feature/ prefixes. Good examples are: fix/signin-issue or feature/issue-templates.

2.2. You have a descriptive commit message with a short title (first line).

2.3. You have only one commit (if not, squash them into one commit).

2.4. yarn run lint doesn't throw any error. If it does, fix them first and amend your commit (git commit --amend).

  1. After these steps, you're ready to open a pull request.

3.1. Give a descriptive title to your PR.

3.2. Provide a description of your changes.

3.3. Put closes #XXXX in your comment to auto-close the issue that your PR fixes (if such).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant