Enforce strict selector validation in getStyleAny and add comprehensive unit tests

[IncharaG26]

Checklist:

• [ x] I have read freeCodeCamp's contribution guidelines.
• [x ] My pull request has a descriptive title (not a vague title like Update index.md)

Closes #64218

This PR resolves an issue in getStyleAny where invalid or partially-matching CSS selectors were incorrectly treated as valid. This behavior allowed users to pass certain curriculum challenges without meeting the required selector constraints.

The fix ensures that only exact matches from the allowed selector list are accepted.

This update improves reliability of curriculum challenge tests such as:

Lab Book Inventory App – Selector Validation
(ref: freeCodeCamp discussions / provided link)

What Was Done
✔ Fixed selector matching logic

Updated the getStyleAny function to prevent:

Partial matching

Attribute-selector misuse

Acceptance of selectors not explicitly allowed

✔ Added complete test coverage

Introduced getStyleAny.test.ts containing:

A failing test for previously-passing invalid selectors

A passing test for correct exact-match selectors

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​types/​assert@​1.5.11
	@​types/​jest@​30.0.0
	@​types/​mocha@​10.0.10
	jsdom@​20.0.3 ⏵ 27.2.0	+1		+1		+31

View full report

[IncharaG26]

Hello team,

By removing erroneous partial matches and enforcing stringent selector validation, this PR improves the getStyleAny utility. To precisely specify the expected behaviour and avoid regressions, I have added a targeted set of unit tests.

Important Enhancements

• To guarantee that partial or invalid selectors cannot pass, exact selector matching was implemented.
• Extensive unit tests covering both valid and invalid cases have been added.
• confirmed that the updated configuration consistently passes unit and integration tests.
• made sure the helper library's unrelated components weren't impacted.
• The behaviour is now fully covered by tests, predictable, and in line with the challenge requirements.

If you would like more test scenarios or improvements, just let me know; I'd be pleased to iterate.
Thank you for taking time to look over this.

[ojeytonwilliams]

Hi, you're welcome to work on this, but getStyleAny already exists on line 502. I recommend starting with that.