Format specifiers in f-strings don't highlight the entire thing in a consistent manner
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
Start by reproducing the two f-string examples in Sublime Text 3.2.1 with MagicPython 1.1.1 and inspect their syntax scopes, comparing them with the regular {test:.2f} example. Done means format specifiers in the reported cases receive a consistent scope, or the behavior is documented as intentional.
Written by the indexing model from the issue text.
Description
Hello. Sometimes the :... aspect of a format string is highlighted in its entirety but often times it's not. I would like to know if it's possible to make it so it's all under the same consistent scope or if it's by design that it doesn't. My main use case has to do with types using a custom __format__.
For example:
I would have imagined both of these to fall under the same scope but they're not.
The first screenshot goes source.python > meta.fstring.python > storage.type.format.python
The second screenshot goes source.python > meta.function-call.python > meta.function-call.arguments.python > meta.fstring.python
A regular line of code without using custom __format__ (e.g. {test:.2f}) goes as source.python > meta.function-call.python > meta.function-call.arguments.python > meta.fstring.python > storage.type.format.python which is what I would expect the other two to return as well, unless it's meant to be treated differently.
- Editor name and version: Sublime Text 3.2.1 Build 3207
- Platform: Windows 8.1
- Color scheme: Custom
- MagicPython version: 1.1.1
- A sreenshot: See above
- 5-10 lines of surrounding code: In the screenshot hopefully
- Dominant language
- JavaScript
- Stars
- 1.4k
- Forks
- 98
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from MagicStack/MagicPython
-
Difficulty 3/5 1-2 days Newbie friendliness 58/100
MagicStack/MagicPython#275 · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
MagicStack/MagicPython#273 · 7 reactions ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
MagicStack/MagicPython#269 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 42/100
MagicStack/MagicPython#267 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 42/100
MagicStack/MagicPython#265 · 2 comments ·
All issues in MagicStack/MagicPython
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
docToolchain/docToolchain#1705 ·
-
Timezone select lists one option per character; duplicate "Failed" reason; shared tracker popover id Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
nightscout/nocturne#1414 ·
-
bug v2
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
modelcontextprotocol/inspector#2458 · 1 comment ·
-
Mend: dependency security vulnerability status: needs triage 🕵️♀️
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
carbon-design-system/ibm-products#9907 ·