Tags

category tells you the shape of a utility — whether it is a hook, a plain util, a predicate. Tags tell you what it is for, and they cut across every category: the answer to "how do I change the query before it hits the adapter?" is a hook in one case and a util in the next.

The vocabulary is closed and deliberately small, so a tag stays useful as a filter. Pick one to see everything carrying it, or filter the hooks and utilities tables directly.

Context

Which part of the service call the utility reads or changes. Reflects the primary target — a few utilities legitimately touch more than one.

context

Reads the call itself — method, type, path, id, service — or the context as a whole, rather than one of its payloads. (4)

query

Reads or rewrites params.query. (24)

data

Reads or rewrites context.data for create/update/patch. (25)

result

Reads or rewrites context.result. (12)

params

Operates on params as a whole, beyond the query — provider, route, pagination, custom keys. (8)

Topic

What the utility is about.

control-flow

Decides whether or in which order other hooks run, rather than touching the call itself. (14)

validation

Rejects a call that does not meet a requirement. (7)

authorization

Restricts what a caller may do or see, based on provider, user, or rate. (6)

multi

Concerns the multi flag or the single-vs-many shape of data and results. (8)

batching

Splits one logical operation into several service calls, or bundles several into one. (6)

pagination

Concerns $limit/$skip or the paginated result shape. (7)

relations

Propagates a change to records of another service. (2)

events

Concerns the service events Feathers emits. (2)

caching

Stores and reuses the outcome of a call. (1)

debugging

Makes a call observable — logging, serializing, inspecting context. (4)

testing

Written for test code — asserting what a service was asked to do, or awaiting what it does. (2)