added sourceName info: create-item & project tuts

[licon4812]

Summary

Added sourceName information to the create-item and create-project cli tutorials as it is an essential property when creating dotnet cli templates

---

Internal previews

📄 File	🔗 Preview link
docs/core/tutorials/cli-templates-create-item-template.md	Tutorial: Create an item template
docs/core/tutorials/cli-templates-create-project-template.md	Create a project template for dotnet new

[tdykstra]

@adegeo Please review.

[adegeo]

Thank you for this submission! I've added a few corrections and suggestions. I think the item template article doesn't need this at all.

[licon4812]

Thank you for this submission! I've added a few corrections and suggestions. I think the item template article doesn't need this at all.

@adegeo

The sourceName doesn't just work with the project templates it is also used for items as well. So that the namespace and class file name is set based on user input

[adegeo]

The namespace must be System because it's an extension method. However, I think at the time I was more hung up on "namespace..." really this could be used for the class name and file name of the class. I'll update those to match in your PR and approve this. Thanks!

[adegeo]

Actually, I was just playing around with this and I don't think it makes sense for the item template. If the user doesn't provide a name, the class name and file name both get created with the same name as the folder. That isn't really a good experience. For the project template, this value makes 100% sense. But not in the item template. Really this needs an optional variable that you could pass into the template.

[adegeo]

OK I looked it up and figured out how to do optional template parameters. It's a big more complicated and requires some more explanation in the article. I actually happen to be working on updating these articles this week (with more modern C# code and other little fixes). If you would like, I can add that stuff to my rewrites. We could just remove the item template content from this PR and push through the project template updates. How does that sound? Or you could update the article too 😁 Let me know what you want to do.

The code for the template is:

{
    "$schema": "http://json.schemastore.org/template",
    "author": "Me",
    "classifications": [ "Common", "Code" ],
    "identity": "ExampleTemplate.StringExtensions",
    "name": "Example templates: string extensions",
    "shortName": "stringext",
    "tags": {
      "language": "C#",
      "type": "item"
    },
    "symbols": {
      "ClassName":{
        "type": "parameter",
        "description": "The name of the code file and class.",
        "datatype": "text",
        "replaces": "StringExtensions",
        "fileRename": "StringExtensions",
        "defaultValue": "StringExtensions"
      }
    }
  }

And you'll need to explain that section. You can see what parameters are allowed with the following command:

dotnet new stringext -?
Example templates: string extensions (C#)
Author: Me

Usage:
  dotnet new stringext [options] [template options]

Options:
  -n, --name <name>       The name for the output being created. If no name is specified, the name of the output directory is used.
  -o, --output <output>   Location to place the generated output.
  --dry-run               Displays a summary of what would happen if the given command line were run if it would result in a template creation.
  --force                 Forces content to be generated even if it would change existing files.
  --no-update-check       Disables checking for the template package updates when instantiating a template.
  --project <project>     The project that should be used for context evaluation.
  -lang, --language <C#>  Specifies the template language to instantiate.
  --type <item>           Specifies the template type to instantiate.

Template options:
  -C, --ClassName <ClassName>  The name of the code file and class.
                               Type: text
                               Default: StringExtensions

[licon4812]

@adegeo Thank you for the feedback. I have modified the explanation of the create-item-template to match the information you have provided.

I figured we should both item and project template files in this PR to avoid having multiple PRs for only 2 files.

[adegeo]

Thanks again!