Ewen Donald Cameron

Apologies, I did not realise the sandbox was set to private by default, I have made it public. I did not provide a TypeScript playground link because I was struggling...

Thank you for the fix @DamianOsipiuk! This allows us to adopt the much better `queryOptions()` pattern

This is a big blocker for our company dropping HTML from our translation messages. We'd like to avoid dangerously setting HTML with our translations, but the current API forces us...

That doesn't align with my experience. I've found in the given example that the superclass constructor always shows above the subclass definition, and setting multipleDefinitions just causes you to always...

Frustratingly I cannot reproduce in a minimal reproduction, only in our actual codebase. When literally copying and pasting our actual code into codeSandbox, it doesn't even show the constructor in...

My issue isn't that it's only showing the constructor or the class, my issue is that it's prioritising jumping to the parent class's constructor instead of the child class's definition....

> Agreed in the VS Code sync to show both the constructor (as the first result) and the class definition (as the second result) when the constructor definition isn't a...

Cool - thank you for clarifying, and thank you for addressing the issue 🙂

Here's me opening a brand new VSCode window, and typing a message without any context. As you can see, the second the message is sent, it gains the @workspace context,...

Hi @lramos15, apologies for the slow response. Yes, this is still occurring for me. https://github.com/user-attachments/assets/3fe9256b-a5af-4a6b-979d-13d6a8087081