Skip to content
GitLab
    • Explore Projects Groups Snippets
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • O openapi-generator
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 3,476
    • Issues 3,476
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 402
    • Merge requests 402
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • OpenAPI Tools
  • openapi-generator
  • Issues
  • #1811
Something went wrong while setting issue due date.
Closed
Open
Issue created 6 years ago by Jim Schubert@jimschubertContributor
  • New related issue

  • Report abuse to administrator

  • New related issue

  • Report abuse to administrator

[REQ] Provide templating authoring details in config-help or generate CLI command (or subcommands of generate)

Open

[REQ] Provide templating authoring details in config-help or generate CLI command (or subcommands of generate)

Is your feature request related to a problem? Please describe.

Yes. The barrier to entry for authoring templates or custom generators should be minimized.

Describe the solution you'd like

config-help should provide some options for displaying more than CLI-only generation flags.

Examples:

  • --authoring => could provide the embeddedTemplateDir as this isn't always the same as the generator name
  • --extensions => could provide a list of vendor extensions for the generator
  • --supporting-files => could provide a list of the supporting files.
  • --features => could list the features supported by the generator (OAuth, JSON/XML, API Key, etc)

Describe alternatives you've considered

We could create a new CLI command, but that seems to add little value over one or more additional switches.

Additional context

I think any additional information should be hidden by default. That is, authoring and extension information shouldn't display when config-help is called for a generator without the additional switches. This is because some of our generators have a ton of options, and there's no need to crowd the terminal output.

The --supporting-files might be non-trivial because many generators conditionally add supporting files based on CLI options passed to the generator. I think we would need to update generators to "register" supporting files and associate them to the options which would lead to those files being generated.

The generated output could eventually be used to generate parts of our documentation (see #1770).

  1. Oh no!

    You are trying to upload something other than an image. Please upload a .png, .jpg, .jpeg, .gif, .bmp, .tiff or .ico.

    Incoming!

    Drop your designs to start your upload.
Tasks
0
server returned results with length 1, expected length of 9

Linked items
0

Link issues together to show that they're related. Learn more.

Activity


Please register or sign in to reply
0 Assignees
None
Assign to
Labels
0
None
0
None
    Assign labels
  • Manage project labels

Milestone
No milestone
None
Due date
None
None
None
Time tracking
No estimate or time spent
Confidentiality
Not confidential
Not confidential

You are going to turn on confidentiality. Only project members with at least the Reporter role, the author, and assignees can view or be notified about this issue.

Lock issue
Unlocked
0
0 participants
Reference:

Menu

Explore Projects Groups Snippets