gRPC coverage changelog update
This commit is contained in:
2
server
2
server
Submodule server updated: 3f4c9dfdfa...6e947f203b
@@ -44,6 +44,48 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
|
|||||||
- **`GetProfileDetails` columns show the SQL type behind them** — the
|
- **`GetProfileDetails` columns show the SQL type behind them** — the
|
||||||
workspace's column list renders `sql_type` from the catalog beside each
|
workspace's column list renders `sql_type` from the catalog beside each
|
||||||
logical type, including for the companion columns the backend generates.
|
logical type, including for the companion columns the backend generates.
|
||||||
|
- **`TableDefinition.GetProfileTree` — `depends_on` is one entry per link** —
|
||||||
|
each dependency now carries the target `table_name` and the `column_name`
|
||||||
|
holding the reference. Both the admin panel and the table-definition
|
||||||
|
workspace render each entry as `table (column)`, so a table that points at
|
||||||
|
one target twice shows as two links.
|
||||||
|
- **`AuthService.Register` — the `role` field is gone** — the request no
|
||||||
|
longer carries a client-chosen role; every registration lands as `guest`.
|
||||||
|
The register page dropped the role input and its suggestion list.
|
||||||
|
|
||||||
|
### Not covered
|
||||||
|
|
||||||
|
The endpoints and fields below are part of the current proto surface but the
|
||||||
|
web crate does not implement them. They are listed so it stays visible what
|
||||||
|
the backend gained that this client has not wired up yet.
|
||||||
|
|
||||||
|
- **`AuthService` role administration** — `SetInitialPassword`, `ListRoles`,
|
||||||
|
`AddRole`, `RemoveRole`, `GrantPermission`, `RevokePermission`,
|
||||||
|
`ListRolePermissions`, `ListGrantableObjects`, `AssignUserRole` and
|
||||||
|
`ListUsers` are not called by any page; there is no role-administration UI.
|
||||||
|
`GetAuthorization` still reads only `role` — the reworked `Permission`
|
||||||
|
object/action surface (structural areas, `data:`/`journal:` objects) is
|
||||||
|
ignored.
|
||||||
|
- **`TableDefinition.PostTableDefinition` — `LINK(table)` columns** — the old
|
||||||
|
per-request link UI was removed when links became columns, and the new
|
||||||
|
spelling is not implemented. The picker offers `link` (the `ListColumnTypes`
|
||||||
|
response marks it declarable), but `COLUMN_TYPE_SPELLING_LINK` is not treated
|
||||||
|
as parameterised, `relation_tables` is loaded but never rendered or applied,
|
||||||
|
and typing `link(table)` is rejected as an unknown type. A link column
|
||||||
|
cannot be declared from the web.
|
||||||
|
- **`TableDefinition.ColumnDefinition.required`** — the new field is always
|
||||||
|
sent as `false`; add-table has no required toggle.
|
||||||
|
- **`TableValidation.DisplayMask.storage_mode`** — the new `MaskStorageMode`
|
||||||
|
option is always left absent (raw); there is no formatted-storage choice in
|
||||||
|
the validation UI.
|
||||||
|
- **`TableScript.ScriptDependency.link_column` / `name_in_script`** — the new
|
||||||
|
dependency fields are not read; the web only surfaces the id and warnings
|
||||||
|
`PostTableScript` returns.
|
||||||
|
- **`TablesData` account as a string** — accounting-enabled tables now take a
|
||||||
|
slash-delimited `account` path instead of the `account_id` reference, and
|
||||||
|
the structure endpoint exposes the column as `account`. The bulk-import and
|
||||||
|
CSV-export paths treat columns generically and were not changed; the web has
|
||||||
|
no accounting data-entry surface of its own.
|
||||||
|
|
||||||
## [v0.8.38] — 2026-08-05
|
## [v0.8.38] — 2026-08-05
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user