Skip to content
GitLab
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
  • #8233
Closed
Open
Issue created Dec 18, 2020 by Administrator@rootContributor

Make Powershell verb parsing for cmdlets optional (or skip it optionally)

Created by: EngineerCoding

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

My API contains several endpoints which for example start with Out, which means that a Out-X cmdlet is generated for these particular endpoints. I don't want this to happen.

Describe the solution you'd like

I would like to make this verb parsing opt-out, so that one can supply an additional argument and this verb parsing is skipped completely. Then the cmdlet would be generated as Invoke-[endpoint].

Describe alternatives you've considered

Post processing my files, but this is hard since I then also have to update all documentation files.

Additional context

I want Out-goingInfo to be named Invoke-OutgoingInfo

Assignee
Assign to
Time tracking