Remove following resolve endpoint #82

Merged
caradoc merged 1 commit from feat/task-f94e6dd2-remove-following-resolve into main 2026-06-01 13:32:49 -05:00
Collaborator

Summary

  • remove the standalone POST /api/v1/following/resolve route
  • keep target normalization behind POST /api/v1/following
  • remove following.resolve from OpenAPI and API/CLI specs
  • update tests for route removal and create-time validation

Verification

  • make check
  • ./scripts/pre-pr.sh

Task: #task-f94e6dd2

## Summary - remove the standalone `POST /api/v1/following/resolve` route - keep target normalization behind `POST /api/v1/following` - remove `following.resolve` from OpenAPI and API/CLI specs - update tests for route removal and create-time validation ## Verification - `make check` - `./scripts/pre-pr.sh` Task: #task-f94e6dd2
feat: remove following resolve endpoint
All checks were successful
CI / build-lint-test (pull_request) Successful in 29s
3ed5def512
Task: #task-f94e6dd2
Author
Collaborator

PR review approved

Summary:

  • Removes the standalone POST /api/v1/following/resolve endpoint.
  • Keeps target parsing/normalization behind POST /api/v1/following.
  • Removes following.resolve from OpenAPI and API/CLI specs.
  • Updates tests to assert the route is gone and validation happens during follow creation.

Acceptance criteria:

  • POST /api/v1/following/resolve is no longer routed — met by route removal and test expecting 404.
  • OpenAPI no longer documents following.resolve — met by deleting the path and route coverage assertion.
  • Following creation still accepts a target and creates a pending record — met by existing create test and retained internal target parsing.
  • Relevant tests and checks pass — make check, ./scripts/pre-pr.sh, and Forgejo CI passed.

Blocking issues: none.

Warnings: none.

Final verdict: approved.

### PR review approved Summary: - Removes the standalone `POST /api/v1/following/resolve` endpoint. - Keeps target parsing/normalization behind `POST /api/v1/following`. - Removes `following.resolve` from OpenAPI and API/CLI specs. - Updates tests to assert the route is gone and validation happens during follow creation. Acceptance criteria: - [x] `POST /api/v1/following/resolve` is no longer routed — met by route removal and test expecting `404`. - [x] OpenAPI no longer documents `following.resolve` — met by deleting the path and route coverage assertion. - [x] Following creation still accepts a target and creates a pending record — met by existing create test and retained internal target parsing. - [x] Relevant tests and checks pass — `make check`, `./scripts/pre-pr.sh`, and Forgejo CI passed. Blocking issues: none. Warnings: none. Final verdict: approved.
caradoc deleted branch feat/task-f94e6dd2-remove-following-resolve 2026-06-01 13:32:49 -05:00
Sign in to join this conversation.
No description provided.