#169654249 bug fix tagging issue on creating articles #77
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
salviosage
requested changes
Nov 11, 2019
nshutijonathan
force-pushed
the
bg-fix-user-tag-on-creating-article-169654249
branch
from
2368683
to
1faf615
Compare
nshutijonathan
force-pushed
the
bg-fix-user-tag-on-creating-article-169654249
branch
from
1faf615
to
5085875
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
-It adds tagging functionality
Description of Task to be completed?
How should this be manually tested?
Any background context you want to provide?
Download or clone the tutorial project code from here, in your terminal then git checkout
bg-fix-user-tag-on-creating-article-169654249, install all required NPM packages by running NPM install from the command line in the project root folder (where the package.json is located).Start the API by running NPM start from the command line in the project root folder, you should see the message Server listening on port 8000. You can test the API directly using an application such as Postman or you can test it with one of the single pages in the browser.
to test authentication and authorization, add this to the header
Key: :x-access-token,value:JWT TOKEN
What are the relevant pivotal tracker stories?
https://www.pivotaltracker.com/story/show/169654249
Screenshots (if appropriate)
Questions: