Skip to content

Conversation

@thecrypticace
Copy link
Contributor

@thecrypticace thecrypticace commented Oct 20, 2025

It was already supposed to work this way — and it appeared via the tests that it did — but the tests weren't loading the design system normally so when we split the legacy utilities into a separate file it stopped testing this properly.

The setup here is a bit iffy but the gist is:

  • We allow static utilities to be suggested by default
  • A static utility can opt out of suggestions by explicitly registering themselves to return none.

Legacy utility registration was moved outside of the utilities file and into compat hooks so this did not test things as intended
@thecrypticace thecrypticace requested a review from a team as a code owner October 20, 2025 23:42
Copy link
Member

@RobinMalfait RobinMalfait left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah makes sense, didn't realise that we weren't loading the design system for intellisense tests properly 😬

@thecrypticace
Copy link
Contributor Author

Yeah… me either 🤦‍♂️

@thecrypticace thecrypticace merged commit 3a4ab82 into main Oct 21, 2025
7 checks passed
@thecrypticace thecrypticace deleted the feat/do-not-suggest-legacy-utilities branch October 21, 2025 10:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants