Write docs/services.all.json with every endpoint - #31
Merged
Merged
Conversation
added 2 commits
September 29, 2026 18:11
services.json keeps only frontend-facing endpoints. Tools that drive a running backend (EndpointRunner) need the backend-only ones too, such as pays.online's WatcherIngest; services.all.json has every endpoint with the same enums and structs.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
docs/services.json lists only frontend-facing endpoints, so EndpointRunner cannot call or role-sweep a backend-only endpoint. pays.online-backend#146 works around it with scripts/utils/services_all.sh; this makes the generator write docs/services.all.json (every endpoint, same enums/structs) beside it, and services.json stays byte-identical.
28 tests pass (new docs-output coverage), clippy and fmt clean.