Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

[Repo] Create Solution Filters or some solution for managing size of toolkit #3270

Closed
michael-hawker opened this issue May 6, 2020 · 3 comments
Labels
build 🔥 feature request 📬 A request for new changes to improve functionality maintenance ⚙️
Milestone

Comments

@michael-hawker
Copy link
Member

Describe the problem this feature would solve

The toolkit is huge. We tried breaking out the graph controls, but that caused it's own issues with dependencies. We need a solution which allows us to build the toolkit in its entirety, but at the same time make it easier to have a fast dev cycle for development of specific components be it .NET specific, a certain control, etc...

Ideally too the sample app should be also able to be loaded with just a single sample so that it can be built/run quickly just like creating a file new project would. This would encourage easier integrations in the toolkit from the start when working on new things vs. an afterthought or extra work from copying things over from a new project template.

Describe the solution

??? Not sure if git submodules make sense or solution filters or some other system ...???

Describe alternatives you've considered

Additional context & Screenshots

@michael-hawker michael-hawker added maintenance ⚙️ feature request 📬 A request for new changes to improve functionality build 🔥 labels May 6, 2020
@ghost
Copy link

ghost commented May 6, 2020

Hello, 'michael-hawker! Thanks for submitting a new feature request. I've automatically added a vote 👍 reaction to help get things started. Other community members can vote to help us prioritize this feature in the future!

@michael-hawker
Copy link
Member Author

We'd also talked about having a sub-module to our documentation repo to make it easier to include/validate docs within the sample app rather than requiring our current 'special' convention.

@Nirmal4G
Copy link
Contributor

Nirmal4G commented Mar 6, 2021

I propose we should reorganize the repository with all the consumer projects that @windows-toolkit have. I don't know why you split them in the first place!! If we do want to split into several repos, at least split them according to target platform like UWP, Win32 and Pure .NET or component-wise like Microsoft Graph, Xaml Islands, etc...

I have a few ideas on repo structure that should help us at managing them better. I'll try them to see what works better and post the tree output here. Then we can decide which one is better for the toolkit repository. But before that I need to know if we're going for the monorepo or not.

@michael-hawker michael-hawker modified the milestones: 7.0, 7.1 Mar 9, 2021
@michael-hawker michael-hawker modified the milestones: 7.1, 7.2/8.0? Aug 31, 2021
@CommunityToolkit CommunityToolkit locked and limited conversation to collaborators Jul 29, 2022
@LalithaNadimpalli LalithaNadimpalli converted this issue into discussion #4661 Jul 29, 2022

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
build 🔥 feature request 📬 A request for new changes to improve functionality maintenance ⚙️
Projects
Status: Done
Development

No branches or pull requests

2 participants