Features

Saves every file of a feature

files is the whole feature, lambda.cs first, held to the same rules as a version - including what a version may come to, since the feature becomes one. A feature keeps no history of its saves: pass the revision it was read at, and a save made in the meantime (by an agent, or in another window) is refused rather than silently replaced.

put/lambdas/{privateKey}/features/{feature}/files

Request

  • Base URL: https://genhttp.dev/api/v1
  • URL: https://genhttp.dev/api/v1/lambdas/{privateKey}/features/{feature}/files
  • 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

Query parameters

deployboolean

Whether to put its preview online with what was saved

Request body

Specificationstring nullable

What the user wants from it and why; left out, the one it has is kept

Changestring nullable

What it changes, in one line; left out, the one it has is kept

Revisioninteger nullable

The revision of the feature these files were made from. Given, the save is refused with 409 if the feature was saved again since, instead of replacing that save without a trace.

Response

The feature afterwards, and what came of its preview where that was asked for

Changes

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