-
Notifications
You must be signed in to change notification settings - Fork 465
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
Spike: Investigate Endpoints for File Selection Screen #30005
Comments
*** Site and Folder Navigation
*** Request 2 - Get all the folders by site Endpoint: POST
Getting an array of folders
*** Content by site/folder *** Request 1 getting the content of the folder/site
This retrieves an array of items, with all the folders/items from the request ** Limitations and Considerations
To filter by type of file (in this case, png), send
|
Parent Issue
No response
Task
Investigate and document the necessary endpoints to implement the file selection screen functionality as shown in the provided image. This includes identifying endpoints for retrieving system hosts and folders, as well as endpoints for fetching the contents of specific folders. If existing endpoints are insufficient, propose new endpoint structures.
Time-box
1-2 hours.
Proposed Objective
Documentation
Proposed Priority
Priority 3 - Average
Acceptance Criteria
No response
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
Assumptions & Initiation Needs
No response
Quality Assurance Notes & Workarounds
No response
Sub-Tasks & Estimates
No response
Outcomes
System Hosts and Folders Endpoint:
/api/v1/filesystem/hosts
]{limit: number, offset: number}
]Folder Contents Endpoint:
/api/v1/filesystem/folder-contents
]{hostId: string, folderId: string, limit: number, offset: number}
]Additional Endpoints (if required):
[List any additional endpoints identified or proposed during the investigation]
Limitations and Considerations:
[Note any limitations of existing endpoints or considerations for implementing new ones]
Recommendations:
[Provide recommendations for implementation or further development]
The text was updated successfully, but these errors were encountered: