chore: add license footer

[dkaser]

Summary by CodeRabbit

• Documentation

  • Added complete GNU General Public License v3 documentation

• Chores

  • Removed unused code blocks
  • Improved application initialization

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

A GPL v3 license file was added to the plugin directory. The main page now conditionally initializes a Utils object and displays a license block via a utility method instead of empty script tags.

Changes

Cohort / File(s)	Summary
License Addition src/usr/local/emhttp/plugins/plugin-diagnostics/LICENSE.txt	New file containing full GNU General Public License v3 text (674 lines) with terms, conditions, and usage guidance.
Main Page Updates src/usr/local/emhttp/plugins/plugin-diagnostics/include/Pages/Main.php	Added conditional initialization of $utils variable, aligned spacing for $tr initialization, removed empty <script> blocks, replaced closing HTML structure with getLicenseBlock() method call.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

🚥 Pre-merge checks | ✅ 2

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'chore: add license footer' clearly and concisely describes the main change—adding a license footer to the plugin. It accurately reflects the changeset, which includes adding a LICENSE.txt file and modifying the Main.php file to display the license block.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore/license

---

📜 Recent review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4862113 and 4afef7d.

⛔ Files ignored due to path filters (1)

• src/usr/local/php/unraid-plugin-diagnostics/composer.lock is excluded by !**/*.lock

📒 Files selected for processing (2)

• src/usr/local/emhttp/plugins/plugin-diagnostics/LICENSE.txt
• src/usr/local/emhttp/plugins/plugin-diagnostics/include/Pages/Main.php

🧰 Additional context used

🧬 Code graph analysis (1)

src/usr/local/emhttp/plugins/plugin-diagnostics/include/Pages/Main.php (1)

src/usr/local/php/unraid-plugin-diagnostics/unraid-plugin-diagnostics/Utils.php (1)

• Utils (22-114)

🪛 LanguageTool

src/usr/local/emhttp/plugins/plugin-diagnostics/LICENSE.txt

[style] ~18-~18: To make your writing flow more naturally, try moving ‘also’ before the verb.
Context: ...ic License for most of our software; it applies also to any other work released this way by ...

(ALSO_PLACEMENT)

---

[style] ~23-~23: Consider using only “Public” to avoid wordiness.
Context: ...e referring to freedom, not price. Our General Public Licenses are designed to make sure that...

(GENERAL_XX)

---

[style] ~189-~189: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...by exercising rights under this License with respect to the covered work, and you disclaim any ...

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

---

[style] ~419-~419: ‘prior to’ might be wordy. Consider a shorter alternative.
Context: ... the violation by some reasonable means prior to 60 days after the cessation. Moreove...

(EN_WORDINESS_PREMIUM_PRIOR_TO)

---

[style] ~426-~426: ‘prior to’ might be wordy. Consider a shorter alternative.
Context: ...ight holder, and you cure the violation prior to 30 days after your receipt of the notic...

(EN_WORDINESS_PREMIUM_PRIOR_TO)

---

[style] ~437-~437: Consider a more concise word here.
Context: ...are not required to accept this License in order to receive or run a copy of the Program. ...

(IN_ORDER_TO_PREMIUM)

---

[style] ~439-~439: To make your writing clearer, consider a shorter, more direct phrase.
Context: ...tion of a covered work occurring solely as a consequence of using peer-to-peer transmission to rece...

(AS_A_CONSEQUENCE_OF)

---

[uncategorized] ~528-~528: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...conveying the work, and under which the third party grants, to any of the parties who would...

(EN_COMPOUND_ADJECTIVE_INTERNAL)

---

[style] ~534-~534: ‘prior to’ might be wordy. Consider a shorter alternative.
Context: ...nt, or that patent license was granted, prior to 28 March 2007. Nothing in this Licen...

(EN_WORDINESS_PREMIUM_PRIOR_TO)

---

[style] ~545-~545: ‘So as to’ expresses purpose and is used in formal texts. Consider using “to”.
Context: ...e. If you cannot convey a covered work so as to satisfy simultaneously your obligations...

(SO_AS_TO)

---

[style] ~662-~662: This phrase is redundant (‘I’ stands for ‘interface’). Use simply “GUI”.
Context: ...am's commands might be different; for a GUI interface, you would use an "about box". You s...

(ACRONYM_TAUTOLOGY)

🔇 Additional comments (3)

src/usr/local/emhttp/plugins/plugin-diagnostics/LICENSE.txt (1)

1-674: LGTM!

Standard GPL v3 license text added correctly. The static analysis style hints should be ignored as this is a verbatim legal document from the Free Software Foundation that must not be modified.

src/usr/local/emhttp/plugins/plugin-diagnostics/include/Pages/Main.php (2)

11-12: LGTM!

Good use of the null coalescing operator for conditional initialization. This pattern allows $tr and $utils to be pre-initialized (e.g., for testing) while ensuring defaults are created when needed.

---

111-113: LGTM!

The license block is cleanly integrated using the Utils::getLicenseBlock() method, which keeps the license rendering logic centralized and reusable across pages.

_{✏️ Tip: You can disable this entire section by setting review_details to false in your review settings.}

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}