-
Notifications
You must be signed in to change notification settings - Fork 48
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
redcap_file_repo_list()
#549
Labels
Comments
Right now, it looks like API import privileges are required, and I posted this to the community. |
wibeasley
added a commit
that referenced
this issue
Oct 25, 2024
wibeasley
added a commit
that referenced
this issue
Oct 25, 2024
Wow. Swift response! This is something I have missed, and I will get around to testing. Thank you @wibeasley! |
wibeasley
added a commit
that referenced
this issue
Nov 3, 2024
wibeasley
added a commit
that referenced
this issue
Nov 3, 2024
wibeasley
added a commit
that referenced
this issue
Nov 3, 2024
wibeasley
added a commit
that referenced
this issue
Nov 3, 2024
wibeasley
added a commit
that referenced
this issue
Nov 3, 2024
wibeasley
added a commit
that referenced
this issue
Nov 3, 2024
wibeasley
added a commit
that referenced
this issue
Nov 3, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
requested by @agdamsbo, call REDCap's "Export a List of Files/Folders from the File Repository" API endpoint.
@agdamsbo, I assume this is the file tree you were referring to?
Right now, the new
redcap_file_repo_list_oneshot()
works as expected, but it doesn't show the whole repo structure, just one folder per call. If I added something recursive to list the complete repo, would people use it? We haven't really used REDCap's file repo much, and I'm not that familiar with the typical use cases.The text was updated successfully, but these errors were encountered: