-
Notifications
You must be signed in to change notification settings - Fork 3
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
Working on download function with the file name #196
Conversation
…co-harry-attachment trying to merge the backend logics and the frontend
…asset-provenance-tracking into coco-harry-attachment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! Works as expected. Going to hold of on merging until 2024-07-08 meeting since it requires updating the backend which is not automated (yet!)
const blob = await response.blob(); | ||
|
||
// Fetch the attachment name | ||
const nameResponse = await fetch(`${baseUrl}/attachment/${deviceKey}/${attachmentID}/name`, { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we check the response headers for attachment-name
before calling into the attachment/${deviceKey}/${attachmentID}/name
function? If deploying to the cloud resolves the CORS issue, we can avoid making two round trips every time.
Discussed this PR in today's meeting. Will merge after @chihlinc gets a chance to address my comment above and I have time to manually update the back end after merging |
No description provided.