Skip to content

Conversation

@TitasGailius
Copy link
Collaborator

@TitasGailius TitasGailius commented Jan 22, 2026

This PR takes a different approach than #367. Instead of parsing the @props directive and relying on external libraries or extensions, we simply extract the code block and display it on hover.

This results in better looking hover cards that cover complicated cases, all with a much simpler implementation.

Screenshot 2026-01-22 at 19 54 30 Screenshot 2026-01-22 at 19 55 21

Unrelated: This PR also fixes an issue where sometimes duplicate paths were being shown.

@N1ebieski
Copy link
Contributor

@TitasGailius Great work! #366 can be closed as well, because it requires parsed props attributes.

@TitasGailius
Copy link
Collaborator Author

@N1ebieski You're totally right! That's a great point, but I'd really love to find a slightly more elegant solution for parsing the @props directive for autocomplete.

I think the best move is likely extending https://github.com/laravel/vs-code-php-parser-cli/ to support this parsing, rather than adding that logic directly into the templates here.

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.

3 participants