For #145567
This inlines the `main.js` script that webview use. This saves us an extra request at the cost of currently having to maintain two copies of the source from `main.js`
* Allow reusing webview origins across reloads
Currently webviews are always loaded into a unique origin. This keeps them isolated but also means that we can't benefit from caching across window reloads
This change adds a new `origin` option that you can pass to webviews which controls the origin they use. If this origin is not provided, we use a random one instead
We then save off this origin for webview panels and restore it on window reloads. Webviews restore a little faster on window reload
* Update webview fallback version
* Add indicator, fixes#148672
This PR adds a default override indicator to extension-contributed
language-specific default setting overrides.
* Remove indicator from language tag settings
* Add a basic check
* Fix yaml error
* Another attempt to fix the yaml
* update actions versions
* let -> const
* Add hygiene and layering check
* update name
* Add WebviewInitInfo type
This cleanup PR adds a new `WebviewInitInfo` type that brings together the core information needed to create a webview
I've then updated the various webview APIs to use this new type
* Revert frameId -> origin change
* frameId -> iframeId
For #121256
This change adds the current `ouputItem` to the notebook markdown renderer's environment
Renders that extend our markdown renderer can use this to access output item metadata for example
The new `markdown.experimental.validate.fileLinks.skipPaths` setting lets you specify a list of paths (as globs) that should not be validation
This is useful since markdown is used in a range of environments, and sometimes you may need to link to paths that don't exist on disk but will exist on deployment
A few other changes here:
- Adds a quick fix that adds paths to `skipPaths`
- Rename existing settings to use the `.enabled` prefix
- Merge deprecated and prerelease migration extensions
- Support deprecated extensions with settings
- Do not auto migrate deprecated extensions
- Support disallowing install for deprecated extensions
- This makes the body of the pull request non-empty when the commit message consists more than one line.
- The GitHub web client fills the body the same way, too, when you create a pull request.
- Some commit messages consist more than one line, like this one, which is giving more detail about the commit, and can be used as a shortcut to not write the same text when opening a pull request and on GitHub.
- Without these changes, the pull request title will be messed up if the commit message is similar to this.
Co-authored-by: João Moreno <joao.moreno@microsoft.com>
Alexandru Dima
Matt Bierner
Connor Peet
Rob Lourens
SteVen Batten
David Dossett
Raymond Zhao
João Moreno
Johannes Rieken
Martin Aeschlimann
Sandeep Somavarapu
Robo
Tyler James Leonhardt
Daniel Imms
Roj
Harald Kirschner
Anthony Stewart
Ladislau Szomoru