Skip to content

Markdown rendering issues with formatting and down level support #7283

@adityapatwardhan

Description

@adityapatwardhan
  1. Formatting file should be used for MarkdownOptionInfo object instead of the the types file for adding script property.
  2. Down level windows consoles which do not support VT100 escape sequences should be handled gracefully.
  3. Add helpuri fwlink for cmdlets.
  4. Add positional parameter for Path parameter for ConvertFrom-Markdown
  5. Add positional parameter for InputObject for Set-MarkdownOption

Environment data

> $PSVersionTable
Name                           Value
----                           -----
PSVersion                      6.1.0-preview.3
PSEdition                      Core
GitCommitId                    v6.1.0-preview.3
OS                             Microsoft Windows 10.0.17713
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

Metadata

Metadata

Labels

Resolution-FixedThe issue is fixed.WG-Cmdlets-Utilitycmdlets in the Microsoft.PowerShell.Utility module

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions