You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I can see the use cases for this new absolute positioning. But for my use cases (screenshotting and docs) I need the query blocks to be shown on a separate line to the nodes they target. A config option to go back to the old behavior would be appreciated.
I can see that rendererClassic is available for me, so I'm using that now - but a separate option to preserve the separate-line queries would be good.
Reproduction
No reproduction required, since Anthony described this is a deliberate change
Contributes
I am willing to submit a PR to fix this issue
I am willing to submit a PR with failing tests
The text was updated successfully, but these errors were encountered:
Validations
Describe the bug
In 0.*, twoslash node query blocks (^?) were shown on a separate line, like here in the TypeScript docs.
In 1.*, they are shown with position: absolute over the top:
This appears to be a deliberate change to the renderer.
I can see the use cases for this new absolute positioning. But for my use cases (screenshotting and docs) I need the query blocks to be shown on a separate line to the nodes they target. A config option to go back to the old behavior would be appreciated.
I can see that rendererClassic is available for me, so I'm using that now - but a separate option to preserve the separate-line queries would be good.
Reproduction
No reproduction required, since Anthony described this is a deliberate change
Contributes
The text was updated successfully, but these errors were encountered: