Control MarkdownOptions via appsettings

[hishamco]

Related to PR #7443

/cc @deanmarcussen

[agriffard]

I was specifically talking about the Configure method that takes a string with extensions separated by +:
https://github.com/lunet-io/markdig/blob/751c79fce4e92857f861d8af0854a8eff0b29071/src/Markdig/MarkdownExtensions.cs#L539

[hishamco]

I was specifically talking about the Configure method that takes a string with extensions separated by +

I knew that, after that, the dialog goes to appsetting. Am I right?

#7443 (comment)

[agriffard]

The whole goal for me was to be able to enable any extensions with only one appsetting property, not to create one property for all the possible extensions.

[hishamco]

to enable any extensions with only one appsetting property

What if someone want to enable Emoji and keep html disabled?

[agriffard]

What if someone want to enable Emoji and keep html disabled?

nohtml+emojis

[hishamco]

I got what you meant, seems I misunderstood you from the beginning ;) I will update the PR

[hishamco]

@agriffard seems we need to point to all possible values or features that could be used in the docs

[agriffard]

@agriffard seems we need to point to all possible values or features that could be used in the docs

We could add a table with each extension/description in the OrchardCore.Markdown documentation.

[hishamco]

We could add a table with each extension/description in the OrchardCore.Markdown documentation

Could be, but we need to reduce the effort of updating the docs whenever an extension is added or removed, IMHO point to that function may useful, but all the options are open

[deanmarcussen]

We could add a table with each extension/description in the OrchardCore.Markdown documentation.

Looks good, just needs docs.