Skip to content
This repository was archived by the owner on Mar 14, 2024. It is now read-only.

Update Native File System article - #2543

Merged
kaycebasques merged 10 commits into
masterfrom
nfs-v2
Apr 15, 2020
Merged

Update Native File System article#2543
kaycebasques merged 10 commits into
masterfrom
nfs-v2

Conversation

@petele

@petele petele commented Apr 9, 2020

Copy link
Copy Markdown
Contributor

Changes proposed in this pull request:

  • Updates WritableStream
  • Adds serializability of FileHandles

Still TODO:

  • Add comment about getFile only valid while the file hasn't changed
  • Update images
  • Add some sample code for saving file handle to indexed db
  • Verify permissions section has info about permission being for the domain, not the tab.

@petele petele added DO NOT MERGE Actively working on but experimental capabilities content update for issues that do not require new content (only for updates to existing content) labels Apr 9, 2020
@petele
petele requested a review from kaycebasques as a code owner April 9, 2020 20:22
@petele petele self-assigned this Apr 9, 2020
@googlebot googlebot added the cla: yes Contributor has signed the CLA label Apr 9, 2020
@netlify

netlify Bot commented Apr 9, 2020

Copy link
Copy Markdown

Deploy preview for web-dev-staging ready!

Built with commit 04b6643

https://deploy-preview-2543--web-dev-staging.netlify.com

@tomayac

tomayac commented Apr 9, 2020

Copy link
Copy Markdown
Member

Fixes #2542

Comment thread src/site/content/en/blog/native-file-system/index.md Outdated

@tomayac tomayac left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Non-owner LGTM

Co-Authored-By: Thomas Steiner <steiner.thomas@gmail.com>
@googlebot

Copy link
Copy Markdown

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

@googlebot googlebot added cla: no Contributor has not signed the CLA and removed cla: yes Contributor has signed the CLA labels Apr 9, 2020
@petele petele added cla: yes Contributor has signed the CLA and removed cla: no Contributor has not signed the CLA labels Apr 9, 2020
@googlebot

Copy link
Copy Markdown

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

ℹ️ Googlers: Go here for more info.

@mkruisselbrink mkruisselbrink left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mostly this looks great! Some ideas for possible improvements/future improvements.

Also there is this sentence somewhere in there: "In the next few versions of Chrome, installed Progressive Web Apps will also be able to save the handle to IndexedDB and persist access to the file across page reloads." which is no longer applicable. That feature actually now is available for all websites (not just PWAs).

Comment thread src/site/content/en/blog/native-file-system/index.md
Comment thread src/site/content/en/blog/native-file-system/index.md Outdated
Comment thread src/site/content/en/blog/native-file-system/index.md Outdated
Comment thread src/site/content/en/blog/native-file-system/index.md Outdated
Comment thread src/site/content/en/blog/native-file-system/index.md Outdated
Comment thread src/site/content/en/blog/native-file-system/index.md Outdated
Comment thread src/site/content/en/blog/native-file-system/index.md
@googlebot

Copy link
Copy Markdown

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

@googlebot googlebot added cla: no Contributor has not signed the CLA and removed cla: yes Contributor has signed the CLA labels Apr 10, 2020
Comment thread src/site/content/en/blog/native-file-system/index.md Outdated
Comment thread src/site/content/en/blog/native-file-system/index.md Outdated
Comment thread src/site/content/en/blog/native-file-system/index.md Outdated
Comment thread src/site/content/en/blog/native-file-system/index.md Outdated
Comment thread src/site/content/en/blog/native-file-system/index.md Outdated
Comment thread src/site/content/en/blog/native-file-system/index.md Outdated
Comment thread src/site/content/en/blog/native-file-system/index.md
Comment thread src/site/content/en/blog/native-file-system/index.md Outdated
Comment thread src/site/content/en/blog/native-file-system/index.md Outdated
Comment thread src/site/content/en/blog/native-file-system/index.md Outdated
@petele petele added cla: yes Contributor has signed the CLA and removed cla: no Contributor has not signed the CLA labels Apr 10, 2020
@googlebot

Copy link
Copy Markdown

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

ℹ️ Googlers: Go here for more info.

@googlebot

Copy link
Copy Markdown

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

@googlebot googlebot added cla: no Contributor has not signed the CLA and removed cla: yes Contributor has signed the CLA labels Apr 13, 2020
@petele petele added cla: yes Contributor has signed the CLA and removed cla: no Contributor has not signed the CLA labels Apr 13, 2020
@googlebot

Copy link
Copy Markdown

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

ℹ️ Googlers: Go here for more info.

@jpmedley jpmedley changed the title Update Native File System article for Cr82 Update Native File System article Apr 13, 2020
@petele petele assigned kaycebasques and unassigned petele Apr 13, 2020

@kaycebasques kaycebasques left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A couple typos. I'll commit them myself and then merge.

Comment thread src/site/content/en/blog/native-file-system/index.md Outdated
Comment thread src/site/content/en/blog/native-file-system/index.md Outdated
@googlebot

Copy link
Copy Markdown

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

@googlebot googlebot added cla: no Contributor has not signed the CLA and removed cla: yes Contributor has signed the CLA labels Apr 15, 2020
@kaycebasques kaycebasques added cla: yes Contributor has signed the CLA and removed cla: no Contributor has not signed the CLA labels Apr 15, 2020
@googlebot

Copy link
Copy Markdown

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

ℹ️ Googlers: Go here for more info.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

cla: yes Contributor has signed the CLA content update for issues that do not require new content (only for updates to existing content)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants