Skip to content

Pls make apiMethods's summary and descriptionType not mandatory so the original is used by default #423

@jonatiao

Description

@jonatiao

Problem description

Currently the summary and descriptionType are sort of mandatory for the apiMethods flags.

 "apiMethods": [
    {
      "name": "createUser",
      "summary": "Create user",
      "descriptionType": "original",
      "tags": {
        "stage": [
          "dev"
        ]
      }
    },
    {
      "name": "logoutUser",
      "summary": "Logs out current logged in user session",
      "descriptionType": "original",
      "tags": {
        "stage": [
          "dev"
        ]
      }
    }
  ]

Which is kind of odd.
I mean, if I do not set the descriptionType in api-config.json, apicli tells me it's mandatory, should not be null, and if I want to default, I should set to "original". Well, can't we just make it consider using "original" instead of throwing an exception?

The summary is worst, if I do not set it in api-config.json, the summary in the APi is overwriten by empty. apimcli does not complain or have support for a "original".

Feature request

Can we please make apiMethods to change only what we ask for it to change?
For instance, if we declare:

 "apiMethods": [
    {
      "name": "createUser",
      "tags": {
        "stage": [
          "dev"
        ]
      }
    }
  ]

Only the tag stage will be added to the createUser method and nothing else is touched for instance.
I would be nice to have something like this for updating single methods.

thx!

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

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