fix(sdk): local bucket files can't be accessed in simulator #7143
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #4143
#7137 added the main code structure for serving files through an express server when
cloud.Bucket
is locally simulated. However, existing code like thepublicUrl
method was still returning URLs to your file system instead of to the HTTP server. This fixes that bug.Fixing this enables other use cases, for example allowing a web app redirect the URL from the signed URL of a file they uploaded to the actual file (if the bucket is public).
Misc:
publicUrl
can only return URLs to existing files. I'm not sure this is a necessary requirement - the URL structure is effectively part of the contract ofcloud.Bucket
(for all public clouds), and checking if the key exists only hurts performance when apps are compiled to the cloud.Checklist
pr/e2e-full
label if this feature requires end-to-end testingBy submitting this pull request, I confirm that my contribution is made under the terms of the Wing Cloud Contribution License.