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
When using the box package to modularize code, breakpoints in VS Code's R Debugger do not seem to be triggered. This issue does not occur when using source() to load files. Since box isolates environments, it might be causing the debugger to lose track of the code context.
The function hello_world defined in func1.R runs correctly, but breakpoints set inside this function are not triggered when called
code to reproduce : main.R
box::use(
. / func1[hello_world]
)
hello_world()
func1.R
#' @export
hello_world <- function(){
x = c(1,2,3) # Breakpoint added here
print("In here")
return("Hello World")
}
R Debugger Version - v0.5.5
Don't know if this is the right place to open this issue
R version
platform x86_64-w64-mingw32
arch x86_64
os mingw32
crt ucrt
system x86_64, mingw32
status
major 4
minor 4.1
year 2024
month 06
day 14
svn rev 86737
language R
version.string R version 4.4.1 (2024-06-14 ucrt)
nickname Race for Your Life
‘box’ version
'1.2.0'
The text was updated successfully, but these errors were encountered:
Error description
When using the box package to modularize code, breakpoints in VS Code's R Debugger do not seem to be triggered. This issue does not occur when using source() to load files. Since box isolates environments, it might be causing the debugger to lose track of the code context.
The function hello_world defined in func1.R runs correctly, but breakpoints set inside this function are not triggered when called
code to reproduce :
main.R
func1.R
Don't know if this is the right place to open this issue
R version
‘box’ version
'1.2.0'
The text was updated successfully, but these errors were encountered: