Installed and ran Flow (static analysis tool)

.babelrc

@@ -0,0 +1,4 @@
+{
+  "presets": ["@babel/preset-flow"],
+  "plugins": ["babel-plugin-syntax-hermes-parser"],
+}

.flowconfig

@@ -0,0 +1,14 @@
+[ignore]
+
+[include]
+
+[libs]
+
+[lints]
+untyped-type-import=error
+internal-type=error
+deprecated-type-bool=error
+
+[options]
+
+[strict]

.github/workflows/azure-deploy-f24.yml

@@ -19,7 +19,7 @@ jobs:
       ./.github/workflows/test.yaml
 
   build-and-deploy:
-    if: github.repository == 'cmu-313/NodeBB'
+    if: github.repository == 'cmu-313/nodebb-f24-bluesleep'
     needs: lint-and-test
 
     runs-on: ubuntu-latest
@@ -30,25 +30,27 @@ jobs:
       - name: Set up Node.js version
         uses: actions/setup-node@v3
         with:
-          node-version: '20.x'
+          node-version: '20.17.0'
 
       - name: Set up NodeBB
         run: |
-          ./nodebb setup '{"url":"https://nodebb-f24.azurewebsites.net:443",
+          ./nodebb setup '{
+            "url": "https://team-bluesleep-db-g9gncbexhhhjd7em.canadacentral-01.azurewebsites.net:443",
             "admin:username": "admin",
             "admin:password": "${{ secrets.ADMIN_PASSWORD }}",
             "admin:password:confirm": "${{ secrets.ADMIN_PASSWORD }}",
             "admin:email": "[email protected]",
             "database": "redis",
             "redis:host": "${{ secrets.REDIS_HOST }}",
             "redis:port": "6379",
-            "redis:password": "${{ secrets.REDIS_PASSWORD }}" }'
+            "redis:password": "${{ secrets.REDIS_PASSWORD }}"
+          }'
 
       - name: 'Deploy to Azure Web App'
         id: deploy-to-webapp
         uses: azure/webapps-deploy@v2
         with:
-          app-name: 'nodebb-f24'
+          app-name: 'team-bluesleep-db'
           slot-name: 'Production'
-          publish-profile: ${{ secrets.AZUREAPPSERVICE_PUBLISHPROFILE_BFAB97B1AB1441ACA7C63280F91AD3F3 }}
+          publish-profile: ${{ secrets.AZUREAPPSERVICE_PUBLISHPROFILE_8DA38339FCB64169A6856C5D3423DAA8 }}
           package: .

.gitignore

@@ -72,4 +72,5 @@ link-plugins.sh
 test.sh
 
 .docker/**
-!**/.gitkeep
+!**/.gitkeep
+node_modules

README.md

@@ -1,3 +1,4 @@
+[![Review Assignment Due Date](https://classroom.github.com/assets/deadline-readme-button-22041afd0340ce965d47ae6ef1cefeee28c7c493a6346c4f15d667ab976d596c.svg)](https://classroom.github.com/a/ithVU1OO)
 # ![NodeBB](public/images/sm-card.png)
 
 [![Workflow](https://github.com/CMU-313/NodeBB/actions/workflows/test.yaml/badge.svg)](https://github.com/CMU-313/NodeBB/actions/workflows/test.yaml)

UserGuide.md

@@ -0,0 +1,155 @@
+# User Guide
+**Authors**: Angela Kim, Veronica Pimenova, Crystal Cheng, Eric Lin
+
+This is the user documentation for our project. It explains the features, setup instructions, and usage details.
+
+## Table of Contents
+- [Feature Descriptions](#feature-descriptions)
+  - [Feature 1: Anonymous Posting](#feature-1-anonymous-posting)
+  - [Feature 2: isAnswered](#feature-2-isanswered)
+  - [Feature 3: Emoji Reactions](#feature-3-emoji-reactions)
+- [Implementation Details](#implementation-details)
+  - [Feature 1: Anonymous Posting](#implementation-details-feature-1-anonymous-posting)
+  - [Feature 2: isAnswered](#implementation-details-feature-2-isanswered)
+  - [Feature 3: Emoji Reactions](#implementation-details-feature-3-emoji-reactions)
+- [Testing](#testing)
+  - [Feature 1: Anonymous Posting](#testing-feature-1-anonymous-posting)
+  - [Feature 2: isAnswered](#testing-feature-2-isanswered)
+  - [Feature 3: Emoji Reactions](#testing-feature-3-emoji-reactions)
+- [Usage](#usage)
+  - [Feature 1: Anonymous Posting](#usage-feature-1-anonymous-posting)
+  - [Feature 2: isAnswered](#usage-feature-2-isanswered)
+  - [Feature 3: Emoji Reactions](#usage-feature-3-emoji-reactions)
+- [Automated Tests](#automated-tests)
+
+---
+
+## Feature Descriptions
+
+### Feature 1: Anonymous Posting
+The Anonymous Posting feature allows users to make a post without having their name/profile attached to the post publicly. This feature provides more flexibility for users, giving them the option to post anonymously.
+
+**Key Functionality**:
+- **Mark post as anonymous**: When drafting a post, users will see a checkbox that allows them to modify the anonymous status of the post.
+- **Post displays as anonymous**: Upon posting, the post shows up without a profile picture or name associated with the post author.
+
+### Feature 2: isAnswered
+The `isAnswered` feature helps track the status of topics in the forum, allowing users to identify which topics have received a satisfactory response. It is useful for Q&A or support forums where users focus on unanswered queries.
+
+**Key Functionality**:
+- **Mark Topics as Answered**: Users with the necessary privileges can mark a topic as answered.
+- **Display Answer Status**: The status (`Answered` or `Unanswered`) is displayed on the topic list view.
+- **Restrict Marking Privileges**: The ability to toggle the `isAnswered` status can be restricted to specific users.
+
+### Feature 3: Emoji Reactions
+The Emoji Reactions feature lets users express their sentiments on posts by reacting with emojis. This provides a lightweight and intuitive way for users to engage with posts.
+
+**Key Functionality**:
+- **React to Posts**: Users can choose from a set of emojis to react to a post.
+- **View Reactions**: The total number of reactions and specific emojis used are displayed under each post.
+- **Remove Reactions**: Users can remove their reactions if they no longer wish to associate them with a post.
+
+---
+
+## Implementation Details
+
+### Implementation Details: Feature 1 (Anonymous Posting)
+- **Backend Field Handling**: A field `isAnonymous` is added to handle the server requests associated with a post’s anonymity.
+  - Relevant Files: `src/posts/summary.js`, `src/topics/create.js`
+- **Backend Schema**: The schema was expanded to include the `isAnonymous` field to match the response body of operations.
+- **Frontend UI**: A checkbox shows up next to the topic title for users to handle the anonymous state of each post.
+- **Integration**: When the checkbox is checked and a post is published, a frontend trigger reflects this change.
+
+### Implementation Details: Feature 2 (isAnswered)
+- **Backend Schema**: A new column `isAnswered` was added to the `topics` table in the database to store the status of each topic.
+- **API Endpoint (Internal)**:
+  - Endpoint: `/post/:pid/answered`
+  - Method: `PUT`
+  - Body: `{ "isAnswered": true }`
+- **Frontend UI**:
+  - Checkbox Display: A checkbox is added next to each post. It is checked if the post is answered and unchecked if unanswered.
+  - UI Placement: The checkbox is visible both in the main topic list and within the post detail view.
+
+### Implementation Details: Feature 3 (Emoji Reactions)
+- **Backend Schema**: No new column was added. Emoji reactions leverage NodeBB’s existing reaction system.
+- **API Endpoints**:
+  - **Add Reaction**:
+    - Endpoint: `/post/:pid/reaction`
+    - Method: `PUT`
+    - Body: `{ "reaction": "😊" }`
+  - **Remove Reaction**:
+    - Endpoint: `/post/:pid/reaction`
+    - Method: `DELETE`
+    - Body: `{ "reaction": "😊" }`
+- **Frontend UI**:
+  - Emoji Picker: Users see an emoji reaction icon next to the post content. Clicking it opens the emoji picker.
+  - Displaying Reactions: Selected emojis and counts are displayed below the post content.
+
+---
+
+## Testing
+
+### Testing: Feature 1 (Anonymous Posting)
+- **Front-End Testing**:
+  - Verify that the anonymous checkbox is visible in the post creation UI.
+  - Ensure the checkbox hides the user’s name and profile picture when posting.
+- **Back-End Testing**:
+  - Test that the `isAnonymous` field updates correctly in the database.
+  - Verify the anonymous status persists across sessions.
+
+### Testing: Feature 2 (isAnswered)
+- **Front-End Testing**:
+  - Ensure the checkbox toggles between "answered" and "unanswered" states.
+  - Verify the status is reflected correctly in both topic list and detail views.
+- **Back-End Testing**:
+  - Test the API to confirm it updates the `isAnswered` status correctly.
+  - Verify that the database saves and retrieves the correct status.
+
+### Testing: Feature 3 (Emoji Reactions)
+- **Front-End Testing**:
+  - Ensure the emoji picker appears and allows users to react to posts.
+  - Test that the reactions display correctly under the post and can be removed.
+- **Back-End Testing**:
+  - Test the API to confirm reactions are added and removed correctly in the database.
+  - Verify that emoji counts update correctly when multiple users react.
+
+---
+
+## Usage
+
+### Usage: Feature 1 (Anonymous Posting)
+1. **Setting a post as anonymous**:
+   - Under a discussion, click "Create Topic".
+   - Check the "anonymous" checkbox near the post title.
+   - Submit the post.
+2. **Viewing Anonymous Posts**:
+   - The post will display as any other post but without the author’s name or profile picture.
+3. **Permissions**:
+   - Only the original poster can toggle the anonymous status.
+
+### Usage: Feature 2 (isAnswered)
+1. **Marking a Post as Answered or Unanswered**:
+   - Navigate to the post, locate the checkbox next to the title, and toggle it.
+2. **Viewing Status**:
+   - In the topic list and post view, the checkbox will indicate the post's current status.
+3. **Permissions**:
+   - Only the original poster or users with permissions can toggle the answer status.
+
+### Usage: Feature 3 (Emoji Reactions)
+1. **Adding a Reaction**:
+   - Navigate to the post and click the emoji icon.
+   - Select an emoji from the picker, and it will display under the post.
+2. **Removing a Reaction**:
+   - Click on your selected emoji to remove it.
+3. **Viewing Reactions**:
+   - Reactions and counts are visible under the post content.
+
+---
+
+## Automated Tests
+- The automated tests for these features can be found in the `/tests/` directory. These tests cover both front-end and back-end functionality for the Anonymous Posting, isAnswered, and Emoji Reactions features.
+
+**Testing Coverage**:
+- The tests include basic functionality, user interaction scenarios, and edge cases, ensuring the robustness of the features. We believe the tests are sufficient as they verify key user interactions, API calls, and data persistence across sessions.
+
+---

lib/admin/search.js

@@ -0,0 +1,96 @@
+'use strict';
+
+const fs = require('fs');
+const path = require('path');
+const sanitizeHTML = require('sanitize-html');
+const nconf = require('nconf');
+const winston = require('winston');
+const file = require('../file');
+const {
+  Translator
+} = require('../translator');
+function filterDirectories(directories) {
+  return directories.map(dir => dir.replace(/^.*(admin.*?).tpl$/, '$1').split(path.sep).join('/')).filter(dir => !dir.endsWith('.js') && !dir.includes('/partials/') && /\/.*\//.test(dir) && !/manage\/(category|group|category-analytics)$/.test(dir));
+}
+async function getAdminNamespaces() {
+  const directories = await file.walk(path.resolve(nconf.get('views_dir'), 'admin'));
+  return filterDirectories(directories);
+}
+function sanitize(html) {
+  return sanitizeHTML(html, {
+    allowedTags: [],
+    allowedAttributes: []
+  });
+}
+function simplify(translations) {
+  return translations.replace(/(?:\{{1,2}[^}]*?\}{1,2})/g, '').replace(/(?:[ \t]*[\n\r]+[ \t]*)+/g, '\n').replace(/[\t ]+/g, ' ');
+}
+function nsToTitle(namespace) {
+  return namespace.replace('admin/', '').split('/').map(str => str[0].toUpperCase() + str.slice(1)).join(' > ').replace(/[^a-zA-Z> ]/g, ' ');
+}
+const fallbackCache = {};
+async function initFallback(namespace) {
+  const template = await fs.promises.readFile(path.resolve(nconf.get('views_dir'), `${namespace}.tpl`), 'utf8');
+  const title = nsToTitle(namespace);
+  let translations = sanitize(template);
+  translations = Translator.removePatterns(translations);
+  translations = simplify(translations);
+  translations += `\n${title}`;
+  return {
+    namespace: namespace,
+    translations: translations,
+    title: title
+  };
+}
+async function fallback(namespace) {
+  if (fallbackCache[namespace]) {
+    return fallbackCache[namespace];
+  }
+  const params = await initFallback(namespace);
+  fallbackCache[namespace] = params;
+  return params;
+}
+async function initDict(language) {
+  const namespaces = await getAdminNamespaces();
+  return await Promise.all(namespaces.map(ns => buildNamespace(language, ns)));
+}
+async function buildNamespace(language, namespace) {
+  const translator = Translator.create(language);
+  try {
+    const translations = await translator.getTranslation(namespace);
+    if (!translations || !Object.keys(translations).length) {
+      return await fallback(namespace);
+    }
+    let str = Object.keys(translations).map(key => translations[key]).join('\n');
+    str = sanitize(str);
+    let title = namespace;
+    title = title.match(/admin\/(.+?)\/(.+?)$/);
+    title = `[[admin/menu:section-${title[1] === 'development' ? 'advanced' : title[1]}]]${title[2] ? ` > [[admin/menu:${title[1]}/${title[2]}]]` : ''}`;
+    title = await translator.translate(title);
+    return {
+      namespace: namespace,
+      translations: `${str}\n${title}`,
+      title: title
+    };
+  } catch (err) {
+    winston.error(err.stack);
+    return {
+      namespace: namespace,
+      translations: ''
+    };
+  }
+}
+const cache = {};
+async function getDictionary(language) {
+  if (cache[language]) {
+    return cache[language];
+  }
+  const params = await initDict(language);
+  cache[language] = params;
+  return params;
+}
+module.exports.getDictionary = getDictionary;
+module.exports.filterDirectories = filterDirectories;
+module.exports.simplify = simplify;
+module.exports.sanitize = sanitize;
+require('../promisify')(module.exports);

lib/admin/versions.js

@@ -0,0 +1,40 @@
+'use strict';
+
+const request = require('../request');
+const meta = require('../meta');
+let versionCache = '';
+let versionCacheLastModified = '';
+const isPrerelease = /^v?\d+\.\d+\.\d+-.+$/;
+const latestReleaseUrl = 'https://api.github.com/repos/NodeBB/NodeBB/releases/latest';
+async function getLatestVersion() {
+  const headers = {
+    Accept: 'application/vnd.github.v3+json',
+    'User-Agent': encodeURIComponent(`NodeBB Admin Control Panel/${meta.config.title}`)
+  };
+  if (versionCacheLastModified) {
+    headers['If-Modified-Since'] = versionCacheLastModified;
+  }
+  const {
+    body: latestRelease,
+    response
+  } = await request.get(latestReleaseUrl, {
+    headers: headers,
+    timeout: 2000
+  });
+  if (response.statusCode === 304) {
+    return versionCache;
+  }
+  if (response.statusCode !== 200) {
+    throw new Error(response.statusText);
+  }
+  if (!latestRelease || !latestRelease.tag_name) {
+    throw new Error('[[error:cant-get-latest-release]]');
+  }
+  const tagName = latestRelease.tag_name.replace(/^v/, '');
+  versionCache = tagName;
+  versionCacheLastModified = response.headers['last-modified'];
+  return versionCache;
+}
+exports.getLatestVersion = getLatestVersion;
+exports.isPrerelease = isPrerelease;
+require('../promisify')(exports);

lib/als.js

@@ -0,0 +1,7 @@
+'use strict';
+
+const {
+  AsyncLocalStorage
+} = require('async_hooks');
+const asyncLocalStorage = new AsyncLocalStorage();
+module.exports = asyncLocalStorage;