service configure upgrade & API simplification - #27
Merged
ronibhakta1 merged 1 commit intoJul 31, 2026
Conversation
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
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.
This pull request updates the
/serviceAPI and related documentation to surface provider-level defaultqualityandcontrolsfields, making it easier for clients to determine what features each provider supports (including unsupported features, which are now explicitly marked asfalse). The code, schema, tests, and docs have all been updated to reflect this new shape.API and Schema Changes:
/serviceendpoint now includesqualityand a fullcontrolsmap (with both enabled and disabled features) for each provider, allowing clients to see what each provider is capable of, not just what's enabled for individual voices. [1] [2] [3] [4]Implementation Changes:
as_dictmethod to theControlsclass inapp/schemas/voice.pyto serialize all control features (enabled and disabled) for use in the/serviceresponse.qualityandcontrols.Documentation Updates:
docs/API.mdto document the newqualityandcontrolsfields on/service, with an explanation of the difference between provider-level and voice-level controls, and an updated example response. [1] [2]503 service_not_readywith more detailed causes.Testing:
controlsandqualityfields.Other:
Licensesection to theREADME.md.