1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
//! `EntitlementResource`.
//!
//! Intended fields (see `docs/plans/tamga-rust.plan.md` §J): `name`, `code`,
//! `metadata`, `created`, `updated`.
//!
//! `code` is the stable, developer-facing identifier — `name` is just a
//! display label. `has_entitlement` (in `src/client.rs`) must match on
//! `code`, never `name`. Despite the URL nesting under
//! `/licenses/{id}/entitlements`, these are full `Entitlement` resources,
//! not lightweight junction/relationship records.
/// The `entitlements` JSON:API resource: `{ id, type, attributes }`. Field
/// set matches `tamga-api`'s actual full `EntitlementResource` serializer —
/// confirmed the license-scoped list/get endpoints return this, not the
/// lightweight `LicenseEntitlementResource` junction resource (which only
/// carries `created`/`updated` timestamps).
/// Attributes of an [`EntitlementResource`].