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.

Sign up for GitHub

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

Jump to bottom

Consider specifying "origin private file system"-ness on each "file system locator" #103

Closed
a-sully opened this issue Mar 15, 2023 · 1 comment · Fixed by #110
Closed

Consider specifying "origin private file system"-ness on each "file system locator" #103

a-sully opened this issue Mar 15, 2023 · 1 comment · Fixed by #110

Comments

@a-sully
Copy link
Collaborator

a-sully commented Mar 15, 2023 •
edited
Loading

Context: #96 (comment)
Related to #92

The cleanest way to do this would be to give each locator an optional Storage Bucket (see WICG/storage-buckets), though that API is not yet standardized
@annevk
Copy link
Member

annevk commented Mar 16, 2023

Can we check that the first item in path is the empty string as per #96 (comment)? I realize that is a tad magical so we could define some kind of predicate for it that has a note alongside explaining the situation.

This was referenced Apr 6, 2023
Closed
Merged
a-sully added a commit that referenced this issue Jun 14, 2023
@a-sully
Specify "origin private file system"-ness on a FileSystemHandle
b2644f0 
Gives a FileSystemHandle an "is in an origin private file system" predicate which checks for the empty string in its path

Better defining the OPFS itself (in terms of the Storage spec) is left to a follow-up

Fixes #103
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Specify "origin private file system"-ness on a FileSystemHandle a-sully/fs
2 participants
@annevk @a-sully