Validation of a 'parameter' node about plaster HOT 6 CLOSED

This comment by @rkeithhill suggests this might be about to change.

from plaster.

@MartinSGill After thinking about this some more, I think that not only do I want to change the type value from input to text but I'm also tempted to add a subtype attribute (looking for better name) e.g.

<parameter name="FullName" type="text" subtype="fullname" .../>
<parameter name="Email" type="text" subtype="email" .../>

This would allow the "text" type to share more code (instead of the current duplication). The only thing I don't like is I don't know how in XML schema to disallow the subtype attribute when the value of the type attribute is not "text". It might have to be a manual validation check.

That said, this would allow for subtypes like: filename, path, version where we could validate the user's input.

from plaster.

Maybe type and content or purpose as names? Just suggesting stuff, subtype would work for me.

from plaster.

Maybe not content since there is a separate content section but keep the suggestions coming.

from plaster.

I thought to the dynamic parameters Powershell.
The error may occur later in the tempalte processing, how to undo an erroneous installation ?

from plaster.

The checks (if any - not sure author or fullname needs validating) will happen in Test-PlasterManifest. That failure will not allow the template processing to start. It will also result in no dynamic parameters being defined. So if you're getting an error about a parameter not being found, run Test-PlasterManifest on the manifest with the -Verbose flag to see what's wrong with the manifest.

from plaster.