Implemented endorse post backend + Fixed Anon Refresh

[savannahxunc]

Anonymous Refresh Fix: This new code fixes the bug that we have been working on with the anonymous refresh. The anonymous name would show up but upon refresh, everything would just revert back to the default settings. There was likely a database overriding that was happening due to the cascading nature of the database. The change was made, but it did not completely update in all parts of the database. Solution: Changed in post.tpl to check a boolean field rather than for a string field.

Endorse post backend: Started implementing the backend for the endorse feature. Because of the headache caused by creating a new field in the database for the anonymous reply feature, I decided to find a work around.

• Utilizing the already existing field of "flags" that allows multiple values to be stored made our lives esaier. We had to add an extra drop down option for flagging called "Endorsed by Admin". After a post was flagged, it would be stored in the database under the flagged field with the specific "Endorsed by Admin" token. This way, We can access this and display it on the front end.

Anonymous Feature Working:

"Flagging" a post as "Endorsed by Admin", first click into the "⋮" menu and click "Flag this Post" then click on the "Endorsed by Admin" in the following screen.

Backend (in Admin dashboard) shows that the post is sucessfully "Endorsed by Admin"

To Dos:
Implement front end display of endorsed post on the top right of a post.

• This would be done by searching in the Database for where the flagged item is equal to "Endorsed by Admin" (exact logic TBD, need to understanf DB better), then display this in the post.tpl file.

resolves #28 and #24

[coveralls]

Pull Request Test Coverage Report for Build 13534500688

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 1 unchanged line in 1 file lost coverage.
• Overall coverage increased (+0.003%) to 82.603%

---

Files with Coverage Reduction	New Missed Lines	%
src/notifications.js	1	79.27%

Totals
Change from base Build 13278022055:	0.003%
Covered Lines:	22378
Relevant Lines:	25666

---

💛 - Coveralls

[joonhoswe]

Savannah, this looks great! I know this is a bug you've been working on for a long time, great work fixing it. I'll go ahead and check out from this branch after merging, and then add the endorse frontend.