# conflict.state

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

Profile: [Errors](https://www.prongs.dev/docs/intents/errors.md) · Raised with: [`fail()`](https://www.prongs.dev/docs/profiles/errors.md) · Status: `409` · Message: yours

## Example

```ts
return fail('conflict.state', 'Create your page first.');
```

The caller gets

```bash
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 for… | 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.

- Built from: [`status.conflict`](https://www.prongs.dev/docs/intents/errors.md#status-conflict)

## For registry authors

**Starter intents.** These are the intents `prongs add errors` puts in your registry, raised with [`fail()`](https://www.prongs.dev/docs/profiles/errors.md). Change the messages to suit your app, and the statuses through the [`status.*`](https://www.prongs.dev/docs/intents/errors.md#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.*`](https://www.prongs.dev/docs/intents/errors.md#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.' },
},
```