When writing conditionals using parenthesis, the first comparison will correctly auto-fill with Intellisense, but all following comparisons within the expression will fail to use Intellisense. This is frustrating as I write a lot of my conditionals using parenthesis, I lose valuable insight as a result, making my workflow more challenging.
This is an example of one of these conditionals not providing Intellisense.
To add onto this, the behavior also extends to interpolated strings, if-then-else ternary expressions, brackets, and interestingly enough, self intellisense (inferred/explicitly annotated).
This behavior is also present in the new type solver
I should note that this behavior was also present back when the “Incremental typechecking and autocompletion in studio” Beta feature was randomly enabled, and considering that this feature is no longer present in the beta features menu, I can only assume it was silently rolled out.
This bug has been present for 2 weeks and has been detrimental to my workflow seeing as a majority of my codebase revolves around the aformentioned features (most significantly involving declarative UI logic). It would be greatly appreciated if any future changes to the base type solver remained strictly optional until the new type solver is confirmed to be fully stable, as to prevent a similar situation from reoccuring.
Update: The self intellisense aspect of this bug has been resolved after 3 weeks in the most recent studio update, however the most significant aspect of the bug (interpolated strings, if-then-else ternary expressions, brackets) is still active…
Hi there, as reported by a creator above, this issue was resolved in July or so. There was more follow-up work to the issues mentioned above as well. We expect that autocomplete should be working great, but please feel free to open any new issues if you’re encountering any problems today.
