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
We're requesting hover intellisense functionality for Re-Editor - the ability to show documentation tooltips when users hover over code identifiers.
Current vs Requested
Currently: Re-Editor supports autocomplete while typing with CodePrompt objects.
Requested: Add ability to show tooltips when hovering over existing code, using the same CodePrompt data.
Implementation Needs
Convert mouse coordinates to text positions
Extract word at position
Display tooltip with relevant documentation
Suggested API
CodeEditor(
enableHoverIntellisense:true,
hoverIntellisenseBuilder: (context, word, prompts) =>DocumentationTooltip(...),
)
This would greatly improve the UX for users reading and writing code in our editor.
The text was updated successfully, but these errors were encountered:
I was looking into something similar and tried to use onEnter and onExit of the TextSpan but it seems to be not possible. Seems like onEnter is overridden in re-editor and does not behave the same way as for normal TextSpan
I was looking into something similar and tried to use onEnter and onExit of the TextSpan but it seems to be not possible. Seems like onEnter is overridden in re-editor and does not behave the same way as for normal TextSpan
Indeed, you must use MouseTrackerAnnotationTextSpan rather than TextSpan.
Feature Request: Hover Intellisense for Re-Editor
Description
We're requesting hover intellisense functionality for Re-Editor - the ability to show documentation tooltips when users hover over code identifiers.
Current vs Requested
Currently: Re-Editor supports autocomplete while typing with
CodePrompt
objects.Requested: Add ability to show tooltips when hovering over existing code, using the same
CodePrompt
data.Implementation Needs
Suggested API
This would greatly improve the UX for users reading and writing code in our editor.
The text was updated successfully, but these errors were encountered: