Skip to content

Add DisableHtml property to MarkdownTextBlock #674

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
May 13, 2025

Conversation

michael-hawker
Copy link
Member

Calls DisableHtml method on Markdig pipeline, as well as not adding any Html based renderer, HtmlBlockRenderer, HtmlEntityInlineRenderer, and HtmlInlineRenderer. When enabled, results in any html tags being ignored and plain-text parts remaining, unformatted.

Committing Patch on behalf of Ameya Kulkarni

@michael-hawker
Copy link
Member Author

We should add a tracking issue to have the Markdown sample expose checkbox options for each of these settings properties so folks can see the behavior change in the output. (Though I think we'd have to make the control re-create the pipeline builder, I think they're all assumed to be set on initialization? Not 100% sure about that.) May be easier if we can switch to using the DependencyProperyGenerator later for all this stuff. :)

@michael-hawker michael-hawker force-pushed the users/ameyak/markdown-htmlflag branch from 442cee7 to 3c4be8a Compare May 9, 2025 23:05
@michael-hawker michael-hawker enabled auto-merge (rebase) May 9, 2025 23:10
@michael-hawker
Copy link
Member Author

FYI @Arlodotexe I think there's an issue with the scoped component build here from #647 (and related). Looks like a part of the CI is still trying to build all the components, but then they're not loaded of course... At least that's what appears to be the case at first glance.

@Arlodotexe
Copy link
Member

Arlodotexe commented May 12, 2025

FYI @Arlodotexe I think there's an issue with the scoped component build here from #647 (and related). Looks like a part of the CI is still trying to build all the components, but then they're not loaded of course... At least that's what appears to be the case at first glance.

It looks like it's tripping on the Test project. The changes in #647 enabled CI to include only components that were updated in the generated solution, but the generated solution also includes a hardcoded wildcard reference to all test shproj in all components.

Since running tests is an integral part of the CI, we cannot simply forgoe building tests to fix the issue. We'll need to fix solution generation to selectively include the tests for the requested components.

Tracking in CommunityToolkit/Tooling-Windows-Submodule#225

Calls DisableHtml method on Markdig pipeline, as well as not adding any Html based renderer, HtmlBlockRenderer, HtmlEntityInlineRenderer, and HtmlInlineRenderer.
When enabled, results in any html tags being ignored and plain-text parts remaining, unformatted.

Committing Patch on behalf of Ameya Kulkarni

Co-authored-by: Ameya Kulkarni <[email protected]>
@michael-hawker michael-hawker merged commit a425dfc into main May 13, 2025
21 of 22 checks passed
@michael-hawker
Copy link
Member Author

Thanks Arlo! Some more work may be needed to support #675 (as I don't know if the control fully listens to all those properties changing dynamically), we can test now at least! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants