Allow Markdown-Rendering Without Providing an Env-Parameter #117041
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes #116987
Since the introduction of the new feature for stabilizing images, passing an
env-parameter to themarkdown-it-parser became mandatory as seen here:vscode/extensions/markdown-language-features/src/markdownEngine.ts
Lines 161 to 168 in a47f324
As my extension uses vscode's
markdown-it-parser, having to provide anenv-object with pre-defined properties is quite inconvenient. For that reason I created this PR which makes passing anenv-object optional as the necessaryenv.containingImages-property is created on the fly, if necessary, using a newinitialize_vscode_image_stabilizer-rule.