Backend integration code for flagging priority questions for faculty issue #12 + NPM test code coverage fix #13
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.
Deleted notifications.js initial changes feature from sprint 1 to fix code coverage and testing to successfully run npm test. Decided to focus on different feature implementation.
Changed topics/create.js, edit.js, posts/create.js, and added priorityflag.js file to implement the backend feature code for issue #12. Feature flags any post with certain priority and assigns a color (green,orange,red) with red being the highest priority to a students post for increased faculty visibility.