Features

Merges a feature as the next version

The feature has to be based on the newest version, and its code has to compile - a version is only ever made of code that compiles. Then its files are saved as the next version, with the feature's specification and change unless the request says others, and the feature is deleted with its preview and its copy of the data. The lambda's own data is not touched, so what the preview wrote is not carried over.

With deploy, the new version is put online as well; deployment says how that went. The version is made either way. The body is optional.

post/lambdas/{privateKey}/features/{feature}/merge

Request

  • Base URL: https://genhttp.dev/api/v1
  • URL: https://genhttp.dev/api/v1/lambdas/{privateKey}/features/{feature}/merge
  • Auth: none declared

Path parameters

privateKeystring required

The editor key of the lambda. Holding it is what allows the call.

featurestring required

The key of the feature, as key in the answer that started it

Request body

Deployboolean nullable

Whether to put the version it becomes online as well

Specificationstring nullable

What the version keeps as what the user wanted; left out, the feature's

Changestring nullable

What the version says it changes; left out, the feature's, or that it merges the feature

Response

The feature was merged as version, and is gone.

Mergedboolean

Whether its files became a version, and the feature is gone

Changes

No recorded changes to this operation across all 1 revision of this API.