-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Split Markdown.* from Controls package. #3437
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
Conversation
…ing the MarkdownTextBlock from the Controls package and decoupling the TextToolbar from the MarkDownFormatter.
Thanks azchohfi for opening a Pull Request! The reviewers will test the PR and highlight if there is any conflict or changes required. If the PR is approved we will proceed to merge the pull request 🙌 |
Microsoft.Toolkit.Uwp.UI.Controls.Markdown.Design/Common/MetadataRegistrationBase.cs
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@QuinnDamerell @paulbartrum your contribution of the MarkdownTextBlock was before my time. I just noticed we had the about.txt file here. Though it looks like you contributed directly, so that was a relicense to the MIT at that time I assume? @deltakosh?
For consistency, I'd like to move this attribution instead to our ThirdPartyNotice file:
QuinnDamerell/UniversalMarkdown (https://github.com/QuinnDamerell/UniversalMarkdown) contributed by Quinn Damerell and Paul Bartrum for the MarkdownTextBlock control, relicensed to this .NET Foundation project under the MIT license upon contribution.
FYI @clairernovotny.
Microsoft.Toolkit.Uwp.SampleApp/SamplePages/TextToolbar/TextToolbarCode.bind
Outdated
Show resolved
Hide resolved
Microsoft.Toolkit.Uwp.SampleApp/SamplePages/TextToolbar/TextToolbarPage.xaml.cs
Outdated
Show resolved
Hide resolved
Microsoft.Toolkit.Uwp.SampleApp/SamplePages/TextToolbar/TextToolbarPage.xaml.cs
Outdated
Show resolved
Hide resolved
Microsoft.Toolkit.Uwp.SampleApp/SamplePages/TextToolbar/TextToolbarPage.xaml.cs
Outdated
Show resolved
Hide resolved
Microsoft.Toolkit.Uwp.UI.Controls.Markdown.Design/Common/MetadataRegistrationBase.cs
Show resolved
Hide resolved
Microsoft.Toolkit.Uwp.UI.Controls/TextToolbar/TextToolbar.Events.cs
Outdated
Show resolved
Hide resolved
Microsoft.Toolkit.Uwp.SampleApp/SamplePages/TextToolbar/TextToolbar.bind
Outdated
Show resolved
Hide resolved
Microsoft.Toolkit.Uwp.UI.Controls/TextToolbar/ToolbarFormatterActiveConverter.cs
Outdated
Show resolved
Hide resolved
@Kyaa-dost was thinking we maybe want another project board to track our more 'backlog'/'debt' items. Like we have a feature/bug board, but this is neither. So maybe we want a 'Technical' bucket for 7.0? And we can use that to track all these breaking changes and other project/repo related work? |
…olbarPage.xaml.cs Co-authored-by: Michael Hawker MSFT (XAML Llama) <[email protected]>
This PR has been marked as "needs attention 👋" and awaiting a response from the team. |
…olbarPage.xaml.cs Co-authored-by: Michael Hawker MSFT (XAML Llama) <[email protected]>
…ts.cs Co-authored-by: Michael Hawker MSFT (XAML Llama) <[email protected]>
Co-authored-by: Michael Hawker MSFT (XAML Llama) <[email protected]>
I contributed directly to the UniversalMarkdown project, @QuinnDamerell as the project owner can speak to licensing. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @paulbartrum looks like we don't have a CLA sign-off on file from you from the original PR contribution where Quinn re-assigned the code. Would you mind signing our CLA here now so that we can just clean-up the history here for the future? Thanks! |
Sure @michael-hawker, done. |
Thanks so much @paulbartrum! That's a great help for resolving this scenario! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Think we're all clear and good to go now! I'll follow-up on anything else later if need be, but think we should be unblocked here.
Hello @michael-hawker! Because this pull request has the p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (
|
Created a new Microsoft.Toolkit.Uwp.UI.Controls.Markdown package, moving the MarkdownTextBlock from the Controls package and decoupling the TextToolbar from the MarkDownFormatter.
Helps with #3145
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Having a dependency on Microsoft.Toolkit.Uwp.UI.Controls pulls too many packages and dependencies.
What is the new behavior?
Microsoft.Toolkit.Uwp.UI.Controls no longer has a dependency on ColorCode.UWP, nor on the Microsoft.Toolkit.Parsers package.
PR Checklist
Please check if your PR fulfills the following requirements:
If you are using MarkdownTextBlock, or the TextToolbar with
Format = Format.Markdown
, you will need to add a dependency to the new Microsoft.Toolkit.Uwp.UI.Controls.Markdown. The MarkdownTextBlock implementation is unchanged, but the TextToolbar no longer has a Format property. The markdown parser is now provided just as any other custom parser, and need to be added in Xaml, or code behind. For example: