Skip to content

Conflict between @range {json} and default parameters #87

@joachimvh

Description

@joachimvh

Using version 3.0.0-beta.7

/**
   * @param parameters - Parameters that should be parsed from the CLI. @range {json}
   *                     Format details can be found at https://yargs.js.org/docs/#api-reference-optionskey-opt
   * @param options - Additional options to configure yargs. @range {json}
   */
  public constructor(parameters: Record<string, Options> = {}, options: CliOptions = {})

Generates the following JSON-LD (same for both parameters):

          "@id": "scs:dist/init/cli/YargsCliExtractor.jsonld#YargsCliExtractor_parameters",
          "range": {
            "@type": "ParameterRangeUnion",
            "parameterRangeElements": [
              "rdf:JSON",
              {
                "@type": "ParameterRangeUndefined"
              }
            ]
          },
          "comment": "Parameters that should be parsed from the CLI."

Should just be rdf:JSON instead of the union.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions