-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Split out Controls.Primitives package. #3660
Split out Controls.Primitives package. #3660
Conversation
Thanks RosarioPulella 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 🙌 |
@michael-hawker Do you think we need to split out the the |
For the Public classes...
And an internal class, |
I've been wondering about this. I would assume we may need to. @azchohfi do you know how these get bundled? They're just included in the package somehow right? I don't know if it'd be weird to keep the aggregated one and only have Design support if you have the full package? As soon as you'd split into the smaller packages nothing would work in VS, right? |
For the other classes already in the namespace. I think that's ok? Those are all more helpers to other controls and probably aren't going to be invoked individually? |
...osoft.Toolkit.Uwp.UI.Controls.Primitives/Microsoft.Toolkit.Uwp.UI.Controls.Primitives.csproj
Outdated
Show resolved
Hide resolved
...osoft.Toolkit.Uwp.UI.Controls.Primitives/Microsoft.Toolkit.Uwp.UI.Controls.Primitives.csproj
Outdated
Show resolved
Hide resolved
...osoft.Toolkit.Uwp.UI.Controls.Primitives/Microsoft.Toolkit.Uwp.UI.Controls.Primitives.csproj
Show resolved
Hide resolved
….Uwp.UI.Controls.Primitives.csproj Co-authored-by: Michael Hawker MSFT (XAML Llama) <[email protected]>
This reverts commit e885c10.
So I split out a |
Microsoft.Toolkit.Uwp.UI.Controls.Primitives/VisualStudioToolsManifest.xml
Show resolved
Hide resolved
[assembly: InternalsVisibleTo("UnitTests.UWP")] | ||
[assembly: InternalsVisibleTo("UnitTests.XamlIslands.UWPApp")] |
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.
I don't know much about how XamlIslands works, do you think we need this for the primitives, @michael-hawker?
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.
This is just exposing it to the XamlIslands tests, so we probably need to tweak those and the Unit Tests as well if they touch these controls?
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.
It seems like the xmal islands test worked just fine without that line.
Remove NeutralResourcesLanguage on attribute on assembly, no resources or language specific code.
If you don't mind @Nirmal4G reviewing my |
Sure @RosarioPulella |
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.
All good here.
|
||
<ItemGroup> | ||
<None Include="VisualStudioToolsManifest.xml" Pack="true" PackagePath="tools" /> | ||
<None Include="$(OutDir)\Design\$(MSBuildProjectName).Design*.dll;$(OutDir)\Design\$(MSBuildProjectName).Design*.pdb" Pack="true" PackagePath="lib\$(TargetFramework)\Design" /> |
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.
Instead of Design*
, we can use DesignTools
as we are not relying on older system anymore. But it's okay now as I still have some cleanup to do with the Design projects.
I'll take it up as part of my next PR. so don't worry about it.
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.
I figured we were going to make that change but I did not want to jump the gun. Thanks @Nirmal4G C:
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.
Seems to work great, thanks Rosario!
Let's merge this into the dev branch and focus on the next one! 🎉🎉🎉
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 (
|
Thanks for helping take a look at this @Nirmal4G, much appreciate your expertise in this area! |
Step towards #3594
Split out
AdaptiveGridView
,DockPanel
,StaggeredPanel
,SwitchPresenter
,UniformGrid
, andWrapPanel
to a new projectMicrosoft.Toolkit.Uwp.UI.Controls.Primitives
.PR Type
What kind of change does this PR introduce?
What is the current behavior?
All of our controls are in a singular
Microsoft.Toolkit.Uwp.UI.Controls
package. For consumers to get anyone package they have to pull in the whole package with all the controls and all there dependencies.What is the new behavior?
AdaptiveGridView
,DockPanel
,StaggeredPanel
,SwitchPresenter
,UniformGrid
, andWrapPanel
are inMicrosoft.Toolkit.Uwp.UI.Controls.Primitives
.PR Checklist
Please check if your PR fulfills the following requirements:
Other information