You can remove the label. The label is optional and will use the value if not present.

This looks like an enum instead of general string.

@hansl If I change this to enum, I get the following build error:

Error: Invalid type enum in JSON Schema at Schema#/properties/implements/items

I realized that the way this is being used the items could be updated to just a list of strings, thank you for pointing that out. Let me know what you think!

Should be something like;

    "implements": {
      "type": "array",
      "description": "Specifies which interfaces to implement.",
      "default": "CanActivate",
      "enum": [
           "CanActivate",
           "CanActivateChild",
           "CanLoad"
      ]
      ....
    },

@alan-agius4 I'm sorry I could be totally missing something (my first time working with json schema 😬), but the x prompt logic requires this array to be named as items: [] as seen in https://github.com/angular/angular-cli/blob/master/packages/angular/cli/models/schematic-command.ts#L311

Are you saying in addition to the x-prompt defintion, also include the enum definition you describe here?

Thanks for your help btw! Just trying to learn and make sure I understand.

Not really, I think it should be something like;

 "implements": {
      "type": "array",
      "description": "Specifies which interfaces to implement.",
      "default": "CanActivate",
      "items": {
        "enum": [
          "CanActivate",
          "CanActivateChild",
          "CanLoad"
        ]
      },
      "x-prompt": {
        "message": "Which interfaces would you like to implement?",
        "type": "list",
        "multiselect": true,
        "items": [
          "CanActivate",
          "CanActivateChild",
          "CanLoad"
        ]
      }
}

The .... above meant, continuation with x-prompt definition.

Note: updated the above is I spotted a mistake

Note also that I have a followup planned to add auto-configuration of multi-select based on the schema. It will eliminate the need to manually specify most of the prompt options and is the reason I originally suggested just using a string constraint for now (this schema would be adjusted in the process either way).

in that case, it LGTM

@clydin would I be able to help out with the implementation of the multi select auto configuration?? I’d love to keep learning and contributing and this could transition well from the work I’ve done so far. Let me know what you think and thanks everyone for the help so far!

@clydin @okeefem2 @alan-agius4 For info, the decision made here causes issues like this one: cyrilletuzi/vscode-angular-schematics#32. The x-prompts is a specific use of the schema, the classic schema properties should be respected for other tools to work (ie. possible values must be in anyOf - or similar, not sure of the good property for this case). For the same reason, implements should be flagged as required (or else it should generate a correct file without it, currently ng g guard without implements generates a file with errors).

you can eventually use the enum type here.

@alan-agius4 Are you saying to create an enum for the values instead of comparing hard coded strings? If yes would this live in the index.ts file or should it have it’s own file?

Hi, the enum is created from the json schema, you don't need to redefine it.

You can run yarn build it will generate an new schema with the enum you created in the json schema.

So you can import it like such

import { Schema as GuardOptions, Implement } from './schema';

Oh very cool. I will make these changes later today when I get home. Thanks!