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
would be great if the parser could identify when brs syntax could be upgraded to bs syntax.
for example, consider:
node.callFunc("funcName", invalid)
this could be : node@.funcName()
The text was updated successfully, but these errors were encountered:
TwitchBronBron
changed the title
provide diagnostic when @. can be used instead of callfunc in brightescript
provide diagnostic when @. can be used instead of callfunc in BrighterScript
Dec 17, 2020
This should be really simple to implement now that codeActions are available. For .bs files, we could emit a hint for every callfunc, that is linked to a code action that recommends switching to callfunc
I guess we wouldn't actually need to add a diagnostic... It could just be shown anytime the cursor is on that line.... But that would get less attention drawn to it.
TwitchBronBron
changed the title
provide diagnostic when @. can be used instead of callfunc in BrighterScript
provide codeAction in .bs when callfunc can be refactored to callfunc operator
Mar 5, 2021
would be great if the parser could identify when brs syntax could be upgraded to bs syntax.
for example, consider:
node.callFunc("funcName", invalid)
this could be :
node@.funcName()
The text was updated successfully, but these errors were encountered: