fix(syntax): remove aggressive python type inference rules #6274
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.


Problem
The current python.scm syntax highlighting queries are too aggressive. They use broad regular expressions to match any identifier starting with a capital letter as a @type or @constructor.
This results in incorrect syntax highlighting behavior, such as:
Variables like Final_Score
Function calls
Even commented text
…being highlighted as Types or Constructors simply because they start with a capital letter.
This leads to inconsistent "rainbow coloring" and reduces readability for Python code displayed inside TextArea.
Solution
The heuristic rules depending solely on regex matching for types and constructors have been disabled.
These were removed in:
File: src/textual/tree-sitter/highlights/python.scm
Removed queries:
((identifier) @type
(#match? @type "^[A-Z].*[a-z]"))
((call
function: (identifier) @constructor)
(#match? @constructor "^[A-Z]"))
This ensures Tree-sitter relies more on proper semantic analysis instead of unreliable capitalization guessing.
The result:
✔ Cleaner syntax highlighting
✔ More accurate code representation
✔ No more distracting false-type coloring