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
See that bar?.() isn't using the method coloring (yellow in my case), but instead the default property coloring (blue in my case)
Expected behavior
Methods using optional chaining should be colored like methods not using optional chaining.
Logs
Log file gives us deep insight into the behavior and performance of the extension. If the issue is a performance
problem or an error occured, please provide the output of the log file below.
Set Angular Log level to verbose.
(I don't think logs are relevant here, but can activate and post if asked)
Screenshots
If applicable, add screenshots to help explain your problem.
🐞 bug report
Is this a regression?
No. Using method optional chaining didn't use to be possible.
Description
As title says, see example image:
Bug Type
What does this bug affect
Reproduction
Steps to reproduce the behavior:
bar: (() => void) | undefined
bar?.()
isn't using the method coloring (yellow in my case), but instead the default property coloring (blue in my case)Expected behavior
Methods using optional chaining should be colored like methods not using optional chaining.
Logs
Log file gives us deep insight into the behavior and performance of the extension. If the issue is a performance
problem or an error occured, please provide the output of the log file below.
Set Angular Log level to verbose.
Screenshots
If applicable, add screenshots to help explain your problem.
See above
🌍 Your Environment
Angular Version:
Extension Version:
VSCode Version:
Operating System:
Extension options:
Anything else relevant?
The text was updated successfully, but these errors were encountered: