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

Distinguish symlinks from regular files and indicate the type of what they point to #6

Open
1 of 24 tasks
kevindice opened this issue May 17, 2018 · 0 comments
Open
1 of 24 tasks

Comments

@kevindice
Copy link

Issue summary

Please provide a short summary of the issue or feature request. Extended descriptions and justification should be placed in the expected behavior section.

What platform services are impacted?

  • Apps
  • Events
  • Files
  • Groups
  • Jobs
  • Logging
  • Metadata
  • Monitors
  • Notifications
  • Templates
  • Postits
  • Profiles
  • Preferences
  • Reactors
  • Realtime
  • Repositories
  • Stats
  • Systems
  • Tags
  • Tenants
  • Transfers
  • Transforms
  • Usage
  • Uuids

To which tenant does this issue apply?

All, but I'm using public.agaveapi.co

What version of the platform are you using?

2.2.19-rb3e2018

Steps to recreate the issue

  1. In a directory X, create
    a. A symlink to a file
    b. A symlink to a directory
    c. A regular file
  2. Using /files/v2/listings/, get a listing of that directory X.

Actual behavior

All three created above have {format: "raw", type: "file"} and are otherwise indistinguishable. The symlink to a directory has the EXECUTE permission, but it still is not distinguishable from an executable file.

Desired behavior

For backwards compatibility, a new bool property such as {symlink: true} could indicate whether a file is a symlink. Using the type property may also be an appropriate way to accomplish this with {type: "file"}, {type: "dir"}, or {type: "symlink"}. It would also be valuable to know whether the symlink points to a file or to a directory. Currently, the only way to tell is to attempt a directory listing and see what happens.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant