Skip to content

Tooltip gets string wrong when it is following an escape character #2510

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
tweakimp opened this issue Sep 6, 2018 · 5 comments
Closed

Tooltip gets string wrong when it is following an escape character #2510

tweakimp opened this issue Sep 6, 2018 · 5 comments
Labels
area-editor-* User-facing catch-all area-intellisense LSP-related functionality: auto-complete, docstrings, navigation, refactoring, etc. bug Issue identified by VS Code Team member as probable bug

Comments

@tweakimp
Copy link

tweakimp commented Sep 6, 2018

Environment data

  • VS Code version: 1.27.1 Insider
  • Extension version (available under the Extensions sidebar): 2018.8.0
  • OS and version: Windows 10 64bit
  • Python version: 3.7
  • Type of virtual environment used (N/A | venv | virtualenv | conda | ...): None

Actual behavior

alt text

Expected behavior

Tooltip shows: Word: str

Steps to reproduce:

  1. Use an escape character right before other string characters.
  2. Hover over other string characters.

Logs

Output for Python in the Output panel (ViewOutput, change the drop-down the upper-right of the Output panel to Python)

None

Output from Console under the Developer Tools panel (toggle Developer Tools on under Help)

None
@brettcannon brettcannon added bug Issue identified by VS Code Team member as probable bug needs verification labels Sep 6, 2018
@brettcannon
Copy link
Member

Can you please verify this, @DonJayamanne ?

@MikhailArkhipov
Copy link

MikhailArkhipov commented Sep 7, 2018

Might be. Conversion of Python docs to markdown is a bit tricky.
microsoft/python-language-server#73

@DonJayamanne
Copy link

DonJayamanne commented Sep 12, 2018

With the new language server we only have the value str, hence not a problem there.
However this is a problem when using the jedi language server.
Will confirm whether this is an issue with Jedi or our implementation.

@DonJayamanne
Copy link

Confirmed, its a bug in the extension.

@gramster gramster added the area-editor-* User-facing catch-all label Oct 10, 2019
@brettcannon brettcannon added area-intellisense LSP-related functionality: auto-complete, docstrings, navigation, refactoring, etc. and removed feature-code documentation labels Apr 9, 2020
@luabud
Copy link
Member

luabud commented Mar 2, 2021

It seems it's been fixed a while ago, so closing it.

@luabud luabud closed this as completed Mar 2, 2021
@ghost ghost removed the needs PR label Mar 2, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 2, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-editor-* User-facing catch-all area-intellisense LSP-related functionality: auto-complete, docstrings, navigation, refactoring, etc. bug Issue identified by VS Code Team member as probable bug
Projects
None yet
Development

No branches or pull requests

6 participants