#18 Cockpit API foundation and read-only security

已关闭
ChenJZ1 周之前创建 · 0 条评论
ChenJZ 评论于 1 周之前

What to build

Establish the versioned, read-only foundation for the city life-line cockpit backend.

Acceptance criteria

  • Schema/DTO defines the AjaxResult payload, camelCase field policy, freshness metadata, requestId and typed error model.
  • API exposes the cockpit version boundary and permits only read operations for the cockpit identity.
  • UI/demo consumer can load an empty map frame and display success-empty, unauthorized and server-error states.
  • Tests cover response serialization, HTTP error categories, service identity enforcement and a request spy proving no business mutation.
  • Demo shows the same read-only contract serving a deterministic empty response and a deterministic error response.

Blocked by

None (can start immediately).

## What to build Establish the versioned, read-only foundation for the city life-line cockpit backend. ## Acceptance criteria - [ ] Schema/DTO defines the AjaxResult payload, camelCase field policy, freshness metadata, requestId and typed error model. - [ ] API exposes the cockpit version boundary and permits only read operations for the cockpit identity. - [ ] UI/demo consumer can load an empty map frame and display success-empty, unauthorized and server-error states. - [ ] Tests cover response serialization, HTTP error categories, service identity enforcement and a request spy proving no business mutation. - [ ] Demo shows the same read-only contract serving a deterministic empty response and a deterministic error response. ## Blocked by None (can start immediately).
ChenJZ2 天之前 关闭
登录 并参与到对话中。
未选择里程碑
未指派成员
1 名参与者
正在加载...
取消
保存
这个人很懒,什么都没留下。