Added Static Analysis Tool: Plato

[alicekang1]

I will preface and say this was not on the 313 Starter List of Static and Dynamic tools, but it was listed on the Other Resources link. I checked with Prof Milton and he said this was okay for having "at least one tool that is not from our starter list".

NOTE: The only test our implementation fails to pass are the lint tests. The TAs mentioned that if we were implementing a different static analysis tool, this is what should be happening (the TAs said it would be okay without the green check mark in this scenario).

Plato is a static analysis tool used to visualize code complexity.

Concrete evidence that you had successfully installed the tool:

• Added plato-report/ to repository
• plato-report/... includes many new files, one being index.html. This file will let you view on a browser the complexity of your code in a readable and interactive UI format.

Concrete evidence that you had successfully installed the tool:

• Provided are screenshots of the index.html file that monitor NodeBB:

[JasmineRocket]

Solid evidence of tool installation by concrete amount of files added to the codebase, tests are working well and tools are functioning properly. Looks good to me!

[coveralls]

Pull Request Test Coverage Report for Build 11563041425

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

• 1 of 1 (100.0%) changed or added relevant line in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.006%) to 82.722%

---

Totals
Change from base Build 11441420770:	0.006%
Covered Lines:	22359
Relevant Lines:	25613

---

💛 - Coveralls

[jullia02]

Successfully added tool reports and added tool to workflow for commits to the main branch, looks good to me!

[jullia02]

Lint Test Failure Status Explanation

The default ESLint workflow check is failing because Plato's configuration does not align with the default ESLint rules. This is expected behavior as Plato has its own linting standards which we want to preserve for consistency. Moreover, changing Plato's code to match the ESLint rules could make future updates and maintenance more difficult. Our dedicated Plato integration workflow (.github/workflows/plato.yml) has passed successfully, confirming that our tool integration is working as intended.

Link: https://github.com/CMU-313/nodebb-f24-sweethearts/actions/runs/11616104264