Template Infrastructure about labs-windows HOT 11 CLOSED

Thanks for that info @mrlacey, FYI #9 shows the prototype we had with dotnet new template (which seems to work pretty well) and some initial testing infrastructure setup examples (though based off before we finalized our current structure for the sample app itself and how it works).

from labs-windows.

part of that is in main already #11

@michael-hawker, what part do you mean? Not the template... do you mean the extra uno requirements? I'm not expecting any conflicts, because all of my work is in the Template folder so far.

I see some good structure from #11 in the CanvasLayout sample. But I'm hesitant to adopt any uno patterns until we've figured out the mechanism to support the uber sample, which #12 seems to be focused on.

I can focus on getting the UI tests working from CI, while you guys handle the uber sample mechanism. Sound good?

from labs-windows.

A new PR for this is now at #76 as the solution structure and requirements have evolved since #9 was worked on.

The biggest changes in the requirements for this are:

• No need to directly integrate the generated experiments with other (All) solutions.
• The inclusion of UI tests has been deferred (until we have confidence in a good multi-targeted solution)

from labs-windows.

The template infrastructure will need to be able to add a reference to the new sample in the uber-sample uwp/wasm heads automatically when the project is created.

from labs-windows.

@michael-hawker @Arlodotexe what do you think about merging in the template before we apply the uno changes? I think this might be a nice checkpoint to settle on the basic template contents and then layer then uno requirements on top.

It's in a good working state, so I'm hoping the tests and template generation to continue to work after we apply the uno upgrade.

from labs-windows.

@shweaver-MSFT part of that is in main already #11, can you see what conflicts you see if you rebase? The other PR #12 Arlo has open is about sample loading for us to handle multiple samples which is relatively isolated still.

from labs-windows.

Yeah, sounds good @shweaver-MSFT! I'll take a look at the template PR in more depth and give it a spin locally. Will let you know if I run into any issues. Thanks!

from labs-windows.

I went through the exercise of porting the UITest projects over from the main toolkit, and I'm not convinced it's the right thing to do. Just because it adds so much extra to the template. We go from one UI test project to four just for the sake of working in the CI. I fear it'll create a ton of duplicated boilerplate test code across the repo, and it's not as dev friendly.

Perhaps we can work it into the uber sample somehow...

from labs-windows.

Considerations

Random bits discovered while fleshing out the sample system that should be taken into consideration for the template system.
Will be updated over time, until we're ready to complete the template infrastructure.

Project template.

• When a new sample project is created, it should be added to
  • Codespace launch config file. See here
  • Multi-sample solution
  • Each deployable multi-sample project head

Sample page template

• Initial sample ID should be unique, scoped to class/namespace. See here

from labs-windows.

VSIX was a suggested alternative, but it doesn't support more than one project at a time. We need to be able to generate multiple projects at once.

Not true ;)
But I get I'm late to this discussion and a VSIX has other limitations that might not be appropriate

from labs-windows.

closed by #76

from labs-windows.