Potential fix for code scanning alert no. 56: Unused variable, import, function or class

[jonobr1]

Potential fix for https://github.com/jonobr1/two.js/security/code-scanning/56

In general, unused variables should either be removed entirely or, if their initialization side effects are required, the initialization should be kept without binding the result to a name. Here, we want to avoid changing behavior: the construction of new Two({...}).appendTo(document.body); should still run, but the unused binding var two = should be removed so there is no unused variable.

The best fix is therefore to replace var two = new Two({ ... }).appendTo(document.body); with a bare expression new Two({ ... }).appendTo(document.body); in the Texture.dispose - Event Unbinding test. This keeps the renderer/DOM setup side effects but eliminates the unused two variable. No new imports, methods, or definitions are required. Concretely, in tests/suite/dispose.js, around line 1145–1150, update that single declaration line to remove var two =.

Suggested fixes powered by Copilot Autofix. Review carefully before merging.

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 4 duplication

Metric	Results
Duplication	4

View in Codacy

_{TIP This summary will be updated as you push new changes. Give us feedback}

[Copilot]

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Removes an unused two variable binding in a dispose test to address a code scanning alert while preserving the side effects of creating/appending a Two instance.

Changes:

• Replaces var two = ... with a bare new Two(...) expression in the Texture.dispose - Event Unbinding test.
• Keeps the renderer/DOM initialization behavior while eliminating the unused variable.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.