How do I run the badge_definitions commands from the shell?

Table of Contents

This file documents the badge_definitions resource at the shell, one section per command. Every command is a subcommand of badge_definitions, and every section exports its own script into projects/ores.shell/scripts/library/. Loading a script runs that one command, so a failure names the command it came from.

1. Commands

1.1. list

Reads one page of the collection. Nothing addresses it but the caller's tenant, so it is the read that shows what exists.

The command is shaped like this:

badge_definitions list [--offset <n>] [--limit <n>] [--order <field>] [--desc]

It is addressed at dq.v1.badge_definitions.list.

badge_definitions list --limit 1

1.2. get

Reads the one row its key addresses. A key states every identifying column, so a partial key is refused rather than answered with an arbitrary row.

The command is shaped like this:

badge_definitions get <code>

It is addressed at dq.v1.badge_definitions.get.

badge_definitions get __none__

1.3. get-many

Reads several rows in one request, one key group per row.

The command is shaped like this:

badge_definitions get-many <code>

It is addressed at dq.v1.badge_definitions.get_many.

badge_definitions get-many __none__

1.4. add

Writes a row. The change states that the row must not exist, so a create that collides with an existing row is refused rather than replacing it. The change carries a reason and a commentary, which the server records on it so the row's history says why it moved.

The command is shaped like this:

badge_definitions add <code> <name> <description> <background_colour> <text_colour> <severity_code> <css_class> <display_order> <reason> <commentary>

It is addressed at dq.v1.badge_definitions.put.

badge_definitions add __none__ __none__ __none__ __none__ __none__ __none__ __none__ 0 system.new_record generated_script

1.5. set

Writes a row. The change states no precondition, so it replaces whatever row the key already addresses. The change carries a reason and a commentary, which the server records on it so the row's history says why it moved. Passing –version makes the write conditional on the version the caller last read.

The command is shaped like this:

badge_definitions set <code> <name> <description> <background_colour> <text_colour> <severity_code> <css_class> <display_order> <reason> <commentary> [--version <n>]

It is addressed at dq.v1.badge_definitions.put.

badge_definitions set __none__ __none__ __none__ __none__ __none__ __none__ __none__ 0 system.new_record generated_script

1.6. put-many

Writes several rows in one request. The count states how many field groups follow. The change carries a reason and a commentary, which the server records on it so the row's history says why it moved.

The command is shaped like this:

badge_definitions put-many --count <n> <code> <name> <description> <background_colour> <text_colour> <severity_code> <css_class> <display_order> <reason> <commentary>

It is addressed at dq.v1.badge_definitions.put_many.

badge_definitions put-many --count 1 __none__ __none__ __none__ __none__ __none__ __none__ __none__ 0 system.new_record generated_script

1.7. delete

Removes a row. The change carries a reason and a commentary, which the server records on it so the row's history says why it moved. Passing –version makes the write conditional on the version the caller last read.

The command is shaped like this:

badge_definitions delete <code> <reason> <commentary> [--version <n>]

It is addressed at dq.v1.badge_definitions.delete.

badge_definitions delete __none__ system.new_record generated_script

1.8. delete-many

Removes several rows in one request. The change carries a reason and a commentary, which the server records on it so the row's history says why it moved.

The command is shaped like this:

badge_definitions delete-many <code> <reason> <commentary>

It is addressed at dq.v1.badge_definitions.delete_many.

badge_definitions delete-many __none__ system.new_record generated_script

1.9. versions

Reads the row's recorded history, newest first.

The command is shaped like this:

badge_definitions versions <code> [--offset <n>] [--limit <n>] [--order <field>] [--desc]

It is addressed at dq.v1.badge_definitions_versions.list.

badge_definitions versions __none__ --limit 1

1.10. version

Reads one recorded version of the row.

The command is shaped like this:

badge_definitions version <code> --version <n>

It is addressed at dq.v1.badge_definitions_versions.get.

badge_definitions version __none__ --version 1

Emacs 29.3 (Org mode 9.6.15)