GitHub

conflict.state

Not possible right now: create your page first, already published

Profile

Errors

Raised with

fail()

Status

409

Message

yours
View as Markdown

Conflict intents

Example

TS
return fail('conflict.state', 'Create your page first.');
The caller gets
Terminal
HTTP 409

{
  "ok": false,
  "error": "Create your page first.",
  "code": "conflict.state"
}

Choosing between neighbours

Find the row that describes your case, and use the intent on the right.

  • If it is

    Use

  • Not possible right now: create your page first, already published

    conflict.state this page

Connections

Declared in the registry, both directions. Where an intent is used in your own code is something check and the gallery see; this site has no app code.

For registry authors

Starter intents. These are the intents prongs add errors puts in your registry, raised with fail(). Change the messages to suit your app, and the statuses through the status.* intents they are built from.

The entry prongs add errors writes into your registry. Change the message here, or the status through its status.* ref.

TS
'conflict.state': {
  kind: 'semantic',
  description: 'Not possible right now: create your page first, already published',
  refs: ['status.conflict'],
  binding: { publicMessage: 'That isn’t possible right now.' },
},