-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Functions not being properly recognized in 2.6.1 #301
Comments
Does it exhibit that behavior with this code? library(R6)
AC <- R6Class("AC",
public = list(
x = 1
)
)
a <- AC$new()
# Press <tab> below
a$ And if not, can you provide a reproducible example? |
@wch With this I can reproduce it:
So then under 2.6.1 you see 'y' as a regular (purple) field and not as a function (blue): This is how it should be (correct under 2.5.1 and also 2.6.0): So then it seems related to the change made in 2.6.1 regarding ".DollarNames.R6(), avoid use of NextMethod()" (#298). I was not able to reproduce on my personal PC where I was using R 4.4.2 and also R 4.1.3, but with a newer build of RStudio. So it may be related to the RStudio IDE most likely, as the change made in 2.6.1 was also made for an issue with the RStudio IDE. To recall, this bug occurs under RSTudio 2024.09.0 Build 375. |
Does the issue persist with the latest daily builds of RStudio? https://dailies.rstudio.com |
The issue occurs on my work device where I unfortunately cannot install a newer version of RStudio. But on my personal PC where I run a newer version of RStudio I cannot reproduce the issue. So it's likely related to the older RStudio builds (RSTudio 2024.09.0 Build 375 on my work device). |
In version 2.6.1, functions are not properly recognized when accessing via '$' sign. This means you can no longer see it is a function, you don't get the automatic '()' when accessing it, and you also aren't shown the arguments of the function.
For illustration, this is how they used to show in 2.5.1:
Now in 2.6.1:
I am on:
(RSTudio 2024.09.0 Build 375)
The text was updated successfully, but these errors were encountered: