api-server

Bug Report Checklist

• [~] Have you provided a full/minimal spec to reproduce the issue?
• Have you validated the input using an OpenAPI validator, yes I used the validate function of the api generator
• [5.0.0 ] What's the version of OpenAPI Generator used?
• Have you search for related issues/PRs?
• What's the actual output vs expected output?

Could be useful to add (beside dbAuth.usernameColumn and dbAuth.passwordColumn) the possibility to configure the request fields (like dbAuth.usernameRequestField) to bind a specific request filed to the relative column of the auth table.

If I'm not mistaken the current state imposes username and password as mandatory fields for the request.

We had an issue where an api user was using the incorrect parameters on an API call. Having this feature would have made the API fail instead of proceeding. The bug would been found earlier.

I can see where this would be a hassle on many cases, But it would be nice for new projects.

I suppose it could be a global config item that could be overridden at the individual action level:

For

It would be great to handle subgroups/subfolders as the following image:

If you PATCHed to /posts/1, but send payload with a different id:

{
  data: {
    id: 789,
    type: 'posts',
    attributes: { ... }
  }
}

We pay attention to the payload and not the URL - instead let's throw an error when there is a mismatch.

Add a GitHub action flow for publishing a new version (run build, run tests, publish to npm and GitHub packates) etc.

https://github.com/sisense/graphql2rest/actions/new

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

Adding routes currently requires the developer to prepare a single list of *Route with all the routes defined in one go. This can be split up and made easier for the developer

Describe the solution you'd like

We can add convenience method for each type of HTTP method supported by webgo (). e.g.

router.A