Updating an existing ChromeOS-only API

[Ben Reich]

Hi team,

I'm from the ChromeOS Files & Storage team who are maintainers of the ChromeOS-only chrome.fileSystemProvider extensions API.

As part of our 2024 goals we are proposing a number of improvements to the API and underlying implementation to make it more ergonomic for cloud filesystems (example).

I had a meta question regarding proposals: is it better to propose all these changes at once? or is it ok to piecemeal the changes as we come across them, in individual proposals?

If the former, is there a supported mechanism to incrementally implement these changes but avoid public facing documentation changes OR reduce the functionality to a single extension as we build out the capability?

Thanks,

Ben