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
{{ message }}
This repository was archived by the owner on Apr 14, 2022. It is now read-only.
f-strings were treated as normal strings before. Now we parse their content, including f-string expressions inside.
We provide completion and hovering for sub-expressions.
Closes#221.
Closes#222.
Closes#223.
Closes#224.
Closes#6.
jakebailey
pushed a commit
to jakebailey/python-language-server
that referenced
this issue
Nov 1, 2019
f-strings were treated as normal strings before. Now we parse their content, including f-string expressions inside.
We provide completion and hovering for sub-expressions.
Closesmicrosoft#221.
Closesmicrosoft#222.
Closesmicrosoft#223.
Closesmicrosoft#224.
Closesmicrosoft#6.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Using the scanned items from #222, tokenize each interpolation and produce an AST.
Example of tokenizing/parsing a string: https://github.com/Microsoft/python-language-server/blob/master/src/Analysis/Engine/Impl/ExpressionFinder.cs
Parsing needs to start at the expression level (https://docs.python.org/3/reference/lexical_analysis.html#f-strings), so likely also needs to call a function similar to
ParseExprStmt
which disallows things like assignment.Epic #6.
The text was updated successfully, but these errors were encountered: