Skip to content
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

ds.ls() and DSLite #175

Open
tombisho opened this issue May 12, 2020 · 5 comments
Open

ds.ls() and DSLite #175

tombisho opened this issue May 12, 2020 · 5 comments
Milestone

Comments

@tombisho
Copy link
Contributor

It seems that ds.ls()/lsDS() need a bit of tweaking to work with DSLite. There is no option to list objects in the parent.frame(). So when you search the global environment, ds.ls() returns the environment containing the DSLite instance and not the objects inside it. It would be useful to have this function when doing development work

@StuartWheater
Copy link
Member

The focus of v6.0 is to support DSI, not DSLite at the moment. But I will try the incorporate a tweak before release.

@ymarcon
Copy link
Member

ymarcon commented May 12, 2020

FYI ds.ls() has always been redundant with the datashield symbols built-in functions (which have been here since the very beginning of datashield).

@tombisho
Copy link
Contributor Author

OK, looks like I have a solution, and if DSLite is out of scope for v6.0 then I can close it?

@StuartWheater
Copy link
Member

The original ds.ls was implemented using an alias to base::ls, at the server-side. The alias to ls has been replaced by a method lsDS. I will looks at this.

@StuartWheater
Copy link
Member

This change appears to require slight change to DSLite. So the changes will be targeted as part of DataSHIELD v6.1

@StuartWheater StuartWheater added this to the v6.1 milestone May 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants