Skip to content
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

Road to MarkdownTextBlock 8.3 stable release #643

Open
Arlodotexe opened this issue Feb 20, 2025 · 2 comments
Open

Road to MarkdownTextBlock 8.3 stable release #643

Arlodotexe opened this issue Feb 20, 2025 · 2 comments

Comments

@Arlodotexe
Copy link
Member

Arlodotexe commented Feb 20, 2025

Background

The new and improved MarkdownTextBlock currently sits in WCT Labs, with several issues open and several fixes in PR.

Problem

There's an increasing need for a reliable, extensible and maintainable MarkdownTextBlock control, especially with the rise of new applications using generative AI.

We'd like to give priority and focus to this control, aiming to graduate it from Labs for the WCT 8.3 stable release.

Solution

There's significant work to do in order to stabilize this control enough for production-ready release.

Generally, we need to track:

  • Bugs and issues
  • Samples and documentation
  • Tests and expected coverage
  • Expected inbox behaviors and configurations
  • Expected points of extensibility (ColorCode, custom renderers, etc)
  • Expected MultiTarget support (uwp, wasdk, wasm, etc)

We can use this ticket to plan and track areas of interest for the 8.3 stable release.

Where needed, subtickets can be created to split up then group the work to avoid clutter here.

Existing tickets should be linked here or under an appropriate subticket.

@michael-hawker
Copy link
Member

Reminder we have this view for experiments as well: https://github.com/orgs/CommunityToolkit/projects/7/views/6 - I added DataTable and MarkdownTextBlock to our parent experiment field that we were missing as well, so we should be able to add the subissues here to the board there as well.

@michael-hawker
Copy link
Member

Note to that this is the original experiment tracking issue, so I think we should just be consolidating this all there vs. having a separate one here? #606 Or at least maybe the sub-issues if we just want to have this one tracking release bits/issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: 🆕 New
Development

No branches or pull requests

2 participants