The `picomatch` library currently checks `process.platform`. This check fails on web, which causes the markdown extension to not load
To fix this, I'm replacing `process.platform` with the string`'web'`
For #30066
This adds a new `documentPaste` api proposal that lets extensions hook into copy and paste.
This can be used to do things such as:
- Create link when pasting an image
- Bring along imports when copy and pasting code
* Bump default JS target for scripts in html
For JS/TS files, we target ES2020 by default. However in html files we're still stuck targetting es6
This change aligns the two
* use es2020.full (includes dom), fix web, avoid searching in node_modules
Co-authored-by: Martin Aeschlimann <martinae@microsoft.com>
This change lets you ignore all links to a given file, even if those links include a header. For example: `[text](/path/to/file#some-header)` can be ignored using `/path/to/file`
* Finalize NotebookEditor api proposal
Fixes#149271
This finalizes most parts of the NotebookEditor api proposal. I haven't removed the proposal entirely as there are still a few parts being left behind:
- The deprecated properties/functions
- A few contribution points such as `notebook/cell/executePrimary`
* remove extra quote
This change renames the experimental skipPaths setting to ignoreLinks. This setting applies to all types of links, and can also be used to ignore links to headers
When reloading windows that need to restore a markdown preview, sometimes I'll see an error when the markdown preview tries accessing a disposed of webview. This seems to be cause caused by `provideTextDocumentContent`, where we end up disposing of the webview before an `await` resumes execution
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
- 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>
* Initial updates
* Add border radius
* Address PR feedback
* Fix typo
* Update shadow blur
* Update LR padding and use description foreground for shortcuts
* Typo
* Fix separator padding/margin
* fix jumpy items in hc themes
* Fix shadow and border radius
* Use opacity for keybinding for better color blend
* Update min width and container padding T/B
* Revert actionbar margin and remove unnecessary menu css file
* Ensure menus respect 0 horizontal margin rule
* set bg/fg color on menu container
* better fix for jumpy menu items
* use outline instead of border
* clean up dead css in style.css
fix opacity for separators in menus
* bring back vertical action bar margins
* Remove old CSS import
Co-authored-by: SteVen Batten <sbatten@microsoft.com>
For #146303
This PR updates the markdown diagnostic reporter to watch linked to files. If one of these linked to files is created or deleted, we recompute the diagnostics for all markdown files that linked to it
For markdown such as `<scope:tag>b</scope:tag>`, we currently detect `<scope:tag>` as an uri (an autolink) and then try validating it as a file path
This change doesn't fix `<scope:tag>` being detected as a link (which is actually correct if there isn't closing html), but does fix the us trying to validate it by marking the uri as external
