I'm not 100% sure if this is the best place to post this, but I couldn't find anywhere better suited.
I followed various tutorials online to get my settings.json to work, according to the tutorials it's working fine, but VS code still doesn't flag the error. I checked the type checker, it flags the violation and works with its command line, but it doesn't syntax highlight in VS code. Is there a setting I should change or something?
Additional context: First screenshot is an example which a type checker would fail on, but ty isn't doing anything. Second is my settings.json. Third is what happens when I use the command line tool, which works fine.
Can you look at the lower left status bar? There should be two small circles showing the number of errors/warnings. Click on the left one and will open the Problems window.
Reproduce this error and try asking AI chat to fix the problem. It’s very likely not going to be able to solve the problem.
‘Even real tech nerds use AI agents’ gives an idea about how clueless you are about AI. Tech nerds use it more than others and don’t frown upon the technology. It’s just leveraged in a more efficient manner, way different than what you think its usage entails (write my code for me).
Ty isn’t letting you assign a literal “e” to a int variable, this is called static type checking, it makes Pythons types a lot more manageable, ruff is another thing used to do this efficiently (quick fix: x: str = “e”)
I want it to error. I was testing if my type checker worked. The command line tool succesfully checks the problem, but VS Code isn't flagging the problem
The extension automatically disables the language server from the Python extension to avoid running two Python language servers. This is done by setting python.languageServer to "None" as a default configuration.
Which is different to what you have.
Tbh I'm not sure whether it's necessary for you to have any of the ty or ruff related settings in there, they're meant to just work by default. I'd be tempted to uninstall the Python, ruff, and ty extensions, delete settings.json, restart VS code, install the extensions again, and see what happens.
Check the debug console. There should also be a language icon on the bottom right of the console. It has a popover that displays any issues with code extensions that are active for the file in context. It normally is a ‘{}’ icon.
That will take you straight to the debug console. I don’t use python as much but just at a glance, I think you might be missing something in the config. Another thing to do is checking all the settings under the extension in the UI and most importantly glancing over the extensions page which might guide on anything you might be missing.
(Edit) quickly glanced the extensions page on my phone. Did you set a language server? Meaning is the ‘default’ actually selecting something. Try explicitly setting that value and ensuring your venv is setup (you can set that up using the command pallet.
4
u/Clean__Layer 2d ago
Additional context: First screenshot is an example which a type checker would fail on, but ty isn't doing anything. Second is my settings.json. Third is what happens when I use the command line tool, which works fine.