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

Poor Developer Experience Arising from Single Solution Across All Samples #781

Open
giusepe opened this issue Dec 26, 2023 · 3 comments
Open

Comments

@giusepe
Copy link
Member

giusepe commented Dec 26, 2023

Is your feature request related to a problem? Please describe.

Currently, we have a single solution that aggregates all samples. While I can appreciate the practicality for maintenance, it becomes confusing when attempting to learn how to build something specific. Additionally, some projects fail to load on a Mac. There are instances of projects with 'hidden' dependencies, such as the MAUI version using Xamarin projects. Lastly, there is what I would describe as 'sensory overload' when attempting to read and understand.

Describe the solution you'd like

Imagine a newcomer or an experienced developer seeking guidance on "how to use RxUI with Blazor." They should navigate to the samples repository, encounter a well-organized readme featuring all current samples along with brief descriptions, and easily locate a folder containing the required sample(s).

Once the sample is downloaded, and the developer opens the solution, the only elements visible to them should be the code relevant to their specific inquiry.

Describe alternatives you've considered

Describe suggestions on how to achieve the feature

The entire solution is divided into three steps:

  1. Split the mega solution into smaller solutions and clean up the projects (I'm submitting a PR for this one right away).
  2. Issue a call to action to create proper READMEs for each project (I can contribute to some, but not all, as I'm not proficient in all the technologies involved).
  3. Update the projects to use the latest SDKs and RxUI.
  4. Develop samples for recent libraries such as Blazor, MAUI, Win App SDK, etc.

Additional context

@giusepe giusepe mentioned this issue Dec 26, 2023
2 tasks
@glennawatson
Copy link
Contributor

slnf files would be probably a better fix here

Have the advantage of being nice on build systems and obtains the goal of making it more user friendly.

@glennawatson
Copy link
Contributor

I have made sln to slnf converters in the past. I will run it over your PR so you aren't wasting any of your time.

@giusepe
Copy link
Member Author

giusepe commented Dec 27, 2023

Slnf, that's new to me. I can give it a go and see how it looks. Should I?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants