mirror of
https://github.com/BerriAI/litellm.git
synced 2026-11-11 08:38:24 +00:00
3069a467d0
* docs(agents): ban semicolons and colons in human-facing text Tighten the writing rule so ";" and ":" are only allowed where the sentence would be nonsensical without them, rewrite the existing semicolons in AGENTS.md to follow it, and note that docs (litellm-docs) keep their trailing "." * docs(agents): rewrite semicolons in nested AGENTS.md files * docs(agents): hand-maintain the dashboard Next.js warning and sync e2e CONTRIBUTING lines * docs(agents): point at the PR template path that exists * docs(agents): restore the generated Next.js block in the dashboard AGENTS.md
1.6 KiB
1.6 KiB
- Shared base and layering rules:
../inference/AGENTS.md - This crate owns provider-independent Messages call orchestration: the entrypoint, call envelopes, provider selection, credential resolution, transport coordination, hooks, and stream lifecycle
- shared API data contracts belong in
litellm-llms-types::formats::messages - adapter contracts and execution inputs in
llms/src/base_llm/messages - provider implementations in
llms/src/<provider>/messages
- shared API data contracts belong in
- Select concrete provider adapters and invoke their contracts
- delegate authentication policy, beta selection, payload rewriting, and response interpretation to those adapters
- keep provider policy out of request preparation and transport handlers
- calling a concrete provider helper for every provider is still a policy dependency
- Route types such as
MessagesCall, prepared requests, and response wrappers containing live streams describe execution. Reuse the shared Messages payload types inside them instead of defining another request or response schema here - The route returns
litellm_host::call::CallOutput: a completed response, or a stream head and chunks - Per-call dependencies are grouped in
litellm_inference::context::CallContext.src/lib.rsexplicitly sequences cache lookup, provider execution, result acceptance (CallContext::result_ready), and cache storage - Preserve the order of validation, normalization, caller-requested parameter removal, and provider transformation when that order affects observable behavior
- Test provider dispatch, auth precedence, header handling, transformations, and responses through behavior, not source structure