Internal refactor: deduplicate shared math in color conversion utilities

[Harishvishwa01]

Most appropriate sub-area of p5.js?

• Accessibility
• Color
• Core/Environment/Rendering
• Data
• DOM
• Events
• Image
• IO
• Math
• Typography
• Utilities
• p5.strands
• WebGL
• DevOps, Build process, Unit testing
• Internationalization (i18n)
• Friendly Errors
• Other (specify if possible)

p5.js version

No response

Web browser and version

No response

Operating system

No response

Steps to reproduce this

Steps:

1. Check out the current main branch of p5.js.
2. Run the existing test suite and lint checks.
3. Apply this refactor and re-run the same tests.

Snippet:

// This change is an internal refactor only.
// No runtime snippet is required because behavior is unchanged.
// Verification is done via existing tests and manual sketches.

[ksen0]

Oh I guess the PR you just made is related to this? In the future please link PR and issue clearly - but also, please do not submit PRs without assignment. Please refer to my comment on your PR about contributor guidelines. Can you explain a bit more clearly what your approach here is and why it's needed? Thank you!

Please note that on 1.x (main branch), only bugfixes are considered. Active development including new features and refactors is on 2.x only (dev-2.0 branch)

[Harishvishwa01]

Thanks for the clarification, and sorry about that — I appreciate you pointing this out.

Yes, this PR is related to the issue I opened. I should have linked them more explicitly and confirmed assignment before submitting that’s my mistake, and I’ll follow the contributor guidelines more carefully going forward.

My intention here was a non-behavioral internal refactor to reduce duplicated math logic in color/color_conversion.js (specifically repeated hue wrapping and lightness→value calculations), while preserving existing behavior and documentation. The motivation was maintainability and reducing the risk of divergence across color conversion paths, not introducing new functionality.

That said, I understand now that refactors are only considered on the 2.x line. I’m happy to close this PR or retarget it to the dev-2.0 branch if that would be more appropriate, and I’ll wait for guidance before proceeding further.

Thanks for your time, and apologies again for the process oversight.