Files
johnnyjoygh 5f3969a830 feat(reactions): add full emoji picker
Let people use any Unicode emoji through a searchable, virtualized
picker.
Keep reaction counts accurate and requests optimistic and idempotent.
Refresh demo content so signed-in visitors can participate.

BREAKING CHANGE: Remove the MEMO_RELATED instance setting and
memoRelatedSetting configuration value. Remove their declarations and
lifecycle references from configuration files; existing reactions are
preserved.
2026-11-14 20:46:46 +08:00
..

Memos API Design

This API design should follow the guidelines and best practices outlined in the Google API Improvement Proposals (AIPs).

The package is memos.api. It carries no version marker; breaking changes are recorded in CHANGELOG.md.

File Layout

  1. The service, then shared top-level types used by more than one group.
  2. One block per resource group, in service order: the resource message, then the group's request/response messages in RPC order, then helper messages used only by that group.

Within a group, order RPCs List, Get, BatchGet, Create, Update, Delete, BatchDelete, then custom methods.

Messages

  • Resources: name first, timestamps (create_time, update_time, others) last.
  • Requests: parent or name, the payload, update_mask, then page_size, page_token, filter, order_by, and other options.
  • Responses: items, then next_page_token.
  • Fields first, then nested enums, then nested messages.
  • Number fields 1..N in declaration order. A new field takes the next number; never reuse or renumber a released field outside a recorded breaking change.
  • google.api.resource lists type, pattern, singular, plural; omit name_field: "name".

Comments

  • Every service, RPC, message, enum and field has a comment. RPC comments start with the RPC name.
  • Fields with google.api.field_behavior start with the matching prefix: Identifier., Required., Optional., Output only., or Input only.. Fields without the annotation get no prefix.
  • Resource-name fields end with a Format: memos/{memo} line.
  • Describe what the server does, not what it might do.