Readonly workspace folders

[isidorn]

• add API that a FileSystemProvider can be readonly
• open readonly files using readonly editors
• disable all context menu commands in the explorer which do not make sense on a readonly resource
• disable all actions (explorer title) that do not make sense on a readonly resource

[IlyaBiryukov]

What granularity is this read-only support going to be? Per workspace, per root, or per file?
There is a feature request for file-level read-onliness, #17670

How about other actions that can potentially mutate user state? Like find-and-replace or code actions?
Is debugging in scope?

Extensions should be able to contribute to how VS Code detects read only status of files. FileSystemProvider is a good place where it could query if a given file (or the whole file system) is read-only.

[isidorn]

@IlyaBiryukov the read only will be per FileSystemProvider - which in practice means per root. Thus each file in that root will be read only. And extensions will be able to contribute this when they register a FileSystemProvider.

As for various actions we will try to support this property in as many places as possible - however this is currently work in progress.

[isidorn]

We have done what we have planned for this milestone -> closing.
If there are subsequent feature requests we can treat them in new issues.

@IlyaBiryukov you can try it out in tomorrow's insiders

[IlyaBiryukov]

@isidorn How a file system provider can change its read-only state once it has been opened by VSCode? The scenario is when read-only limit is lifted or imposed mid session.

[isidorn]

@IlyaBiryukov he can re-register