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
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
In a directory X, create
a. A symlink to a file
b. A symlink to a directory
c. A regular file
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.
The text was updated successfully, but these errors were encountered:
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?
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
a. A symlink to a file
b. A symlink to a directory
c. A regular file
Actual behavior
All three created above have
{format: "raw", type: "file"}
and are otherwise indistinguishable. The symlink to a directory has theEXECUTE
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.The text was updated successfully, but these errors were encountered: