-
-
Notifications
You must be signed in to change notification settings - Fork 357
Adding +=, -=, and others to nonstandardSymbol doesn't fix formatting for that file #1175
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
Reformat nonstandard-symbols, you can't simply say what they are, and I also need to know their grammar features. |
Could you rephrase that? I don't really know what you mean. This is my config file if that helps. {
"editor.formatOnSave": true,
"Lua.runtime.version": "Lua 5.4",
"Lua.diagnostics.disable": [
"undefined-global",
"lowercase-global"
],
"Lua.diagnostics.globals": [
"playdate",
"import"
],
"Lua.runtime.nonstandardSymbol": [
"+=",
"-=",
],
"Lua.workspace.library": [
"$PLAYDATE_SDK_PATH/CoreLibs"
],
"Lua.workspace.preloadFileSize": 1000
} |
This function is not implemented now, but if I want to implement it, a separate configuration may be required |
If you mean you want to know what
Sorry if that's not what you meant. |
Well, although you don't understand what I mean, I'm already working on it, just be patient |
wait #1187 merge |
This issue is marked as closed, though the issue persists for me. It still won't lint. Does the configuration need to be changed or anything? |
What do you mean of 'lint' instead of 'formatting'? |
My bad! Retested and after resaving .vscode configs it seems to work again. Some issue on my end. Closing this again! Thanks for the help. |
Describe the bug
When adding +=, -= and other symbols to
Lua.runtime.nonstandardSymbol
, errors are removed from the "Problems" tab, and compiling is possible again. But formatting the document doesn't work whenfoo += 1
is somewhere in the document.To Reproduce
Steps to reproduce the behavior:
Expected behavior
Code should look like
Environment:
The text was updated successfully, but these errors were encountered: