Normalize journal entry config actions

This commit is contained in:
Scott Idem
2026-05-05 12:59:30 -04:00
parent 0d0cec9819
commit 80957316f2
3 changed files with 387 additions and 221 deletions

View File

@@ -177,6 +177,25 @@ async function load_ae_obj_id__my_obj({ api_cfg, obj_id }) {
}
```
### Shared/Common Aether object fields
The core fields for almost all Aether objects are:
* id/id_random
* code - string
* name - string
* summary - string
* content - string
* alert - boolean
* alert_msg - text
* priority - boolean
* sort - int
* group - string
* hide - boolean
* enable - boolean
* default_qry_str - special concat string index
* notes - text
* created_on - timestamp
* updated_on - timestamp
### ID convention — never use `_id_random` fields
The V3 API uses random string IDs (e.g. `event_file_id = "aBc123"`). The `*_id_random`
fields are legacy aliases. The integer version of the ID is never returned by the API. Always use the short form:
@@ -229,7 +248,7 @@ When looking up a single object by its string ID, always use `.where().equals().
---
## 6. Naming Conventions
## 6. Naming Conventions (snake_case; no camelCase)
| Pattern | Example | Used for |
|---|---|---|