Skip to content

Conversation

@GuySartorelli
Copy link
Contributor

Fixes #76

The typeToArray() implementation is based heavily on typeToString(), but uses the [$type, false] array style that resolveHint() is expecting.

I'm not sure how to go about writing a test for this - I didn't have enough time to get familiar with the way your tests are written. Can you please give me some guidance? It doesn't look like the existing tests include namespaces in a way that would surface this bug and I'm not sure how to add that.

@GuySartorelli
Copy link
Contributor Author

@williamdes Have you had a chance to look at this?

@GuySartorelli
Copy link
Contributor Author

@williamdes Any update on this?

@williamdes
Copy link
Member

Hi
Thanks for the ping, I will process this soon

@williamdes williamdes merged commit ba67a5d into code-lts:main Nov 18, 2025
22 of 39 checks passed
Copy link
Member

@williamdes williamdes left a comment

Choose a reason for hiding this comment

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

Thank you !
I trust your work, even if there is no unit tests.
Let's see how it goes

@williamdes williamdes added this to the v5.6.0 milestone Nov 18, 2025
@williamdes williamdes self-assigned this Nov 18, 2025
@GuySartorelli GuySartorelli deleted the pulls/main/fix-hints branch November 18, 2025 19:57
@GuySartorelli
Copy link
Contributor Author

Fingers crossed I didn't miss anything 😅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

Typehints sometimes incorrectly prepend the current namespace

2 participants