-
Notifications
You must be signed in to change notification settings - Fork 349
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
[Proposal] Ship ReadMe.txt file with packages to inform consumers of necessary steps #273
Comments
Thanks Shaun! Love this idea to help devs get up and running quickly with the .NET MAUI Community Toolkit! 💯 As a part of this effort, could we also add the Getting Started info to our GitHub Repository We can put the Getting Started info in the top of the Getting Started// ... |
Yes great idea! |
Reopening Proposal. Only Proposals moved to the |
Reopening Proposal. Only Proposals moved to the |
I think we can move it to completed |
Reopening Proposal. Only Proposals moved to the |
thanks @VladislavAntonyuk msftbot seemed to want to keep it open for some reason 🤷 |
[FEATURE_NAME] Ship
ReadMe.txt
file with packages to inform consumers of necessary stepsLink to Discussion
This is being raised as a result of discussion #272 where the consumer saw that using a converter in XAML only was reporting build issues.
Summary
Add a README.txt to the NuGet Package that provide guidance to consumers on how to Use the toolkit upon installation.
The Getting Started step should detail the extension method usage to initialise the library:
And then refer the developer on to the docs website for further details.
Also add the Getting Started steps to the GitHub Repository README.md, along with a NuGet Package badge:
Motivation
To make it easier to get going in using the toolkit packages.
Detailed Design
It should involve the addition of a readme.txt to each project and then adding this line to each project:
Usage Syntax
N/A
Drawbacks
We would need to cover what happens if both
CommunityToolkit.Maui
andCommunityToolkit.Maui.Core
are added. We don't need to inform the user they need to use both methods.Alternatives
Do nothing? Leave it in the documentation online.
Unresolved Questions
The text was updated successfully, but these errors were encountered: