Connected back end isResolved with front end isResolved placeholder button #75
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
…tTopicAsResolved controller method
LujainAlMansoori
changed the title
mbfannan
added
the
incorrect workflow fixed by other pr
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.
I added the connection of isResolved using a fake placeholder button. The changed made was to the topics controller (src/controllers/topics.js), adding the method to set the isResolved variable. Also, added the route for this controller method in the src/routes/index.js. This links to issue #67 but this issue is not resolved yet, because of GitHub action workflow test failure, thus it was merged, however test passing issues on GitHub is resolved by pull request #80.