GitHub

record.missing

The thing does not exist, or the caller may not know it does

Profile

Errors

Raised with

fail()

Status

404

Message

yours
View as Markdown

Example

TS
return fail('record.missing', 'Profile not found.');
The caller gets
Terminal
HTTP 404

{
  "ok": false,
  "error": "Profile not found.",
  "code": "record.missing"
}

Choosing between neighbours

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

  • If it is

    Use

  • The thing does not exist, or the caller may not know it does

    record.missing this page

  • A record that does not exist

    rather than request.missing
    record.missing this page

  • Hiding that the thing exists at all

    rather than permission.denied
    record.missing 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
'record.missing': {
  kind: 'semantic',
  description: 'The thing does not exist, or the caller may not know it does',
  refs: ['status.notfound'],
  keywords: ['not found', 'missing', 'unknown', 'no such'],
  binding: { publicMessage: 'Not found.' },
},