Uh oh!
There was an error while loading. Please reload this page.
docs: add reference to MLOps template contract (fixes #151) - #166
docs: add reference to MLOps template contract (fixes #151)#166emberb170d wants to merge 6 commits into
Conversation
📝 WalkthroughWalkthroughThe PR adds FastAPI AI route ownership and conflict documentation, expands the chat extension README, links the MLOps contract, and adds shared editor settings and Python 3.12 declarations to templates. ChangesExtension documentation
Template defaults
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related issues
Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches 💡 1⚔️ Resolve merge conflicts 💡
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs/AUTHORING.md`:
- Around line 410-420: Complete the “Data path collision (modality packs)”
example in docs/AUTHORING.md by showing entries for all three packs:
all-mlops-tabular-data, all-mlops-image-data, and all-mlops-sequence-data. Make
each incompatibleWith list symmetric and include every pairwise conflict,
consistent with the one-modality-pack rule; do not leave the block as a partial
example.
In `@extensions/fastapi-ai-chat/README.md`:
- Line 56: Update the AI_CHAT_PROVIDER documentation in the README to list mock
as the only currently supported provider, removing unimplemented providers from
the supported-values description and optionally labeling them as future
placeholders. Keep the generated template and test behavior consistent with this
documented provider scope.
🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: 1be16644-0eb3-4ac9-9541-4dbd0f7dafe6
📒 Files selected for processing (14)
docs/AUTHORING.mddocs/recipes/FASTAPI_AI_ROUTE_OWNERSHIP.mdextensions/fastapi-ai-chat/README.mdtemplates/celery-worker/.editorconfigtemplates/celery-worker/.python-versiontemplates/cli-starter/.editorconfigtemplates/cli-starter/.python-versiontemplates/django-api/.editorconfigtemplates/django-api/.python-versiontemplates/fastapi-starter/.editorconfigtemplates/fastapi-starter/.python-versiontemplates/mlops-sklearn-starter/.editorconfigtemplates/mlops-sklearn-starter/.python-versiontemplates/uv-workspace-starter/.editorconfig
| **Example 2 — Data path collision (modality packs):** | ||
| ```json | ||
| { | ||
| "name": "MLOps Tabular Data", | ||
| "slug": "all-mlops-tabular-data", | ||
| "incompatibleWith": ["all-mlops-image-data", "all-mlops-sequence-data"] | ||
| } | ||
| ``` | ||
| Competing modality packs overwrite the same `data/` paths. Only one per generated project. |
There was a problem hiding this comment.
🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win
Complete the MLOps conflict matrix.
The example at Lines [413-417] defines only all-mlops-tabular-data. It omits reciprocal declarations for all-mlops-image-data and all-mlops-sequence-data. It also omits the image-to-sequence conflict, although Line [420] says that only one modality pack can be selected.
docs/recipes/FASTAPI_AI_ROUTE_OWNERSHIP.md, Lines [107-108], requires symmetric incompatibleWith pairs. Show all three entries with a complete pairwise matrix, or label this block explicitly as a partial example.
Proposed completion
{
"name": "MLOps Tabular Data",
"slug": "all-mlops-tabular-data",
"incompatibleWith": ["all-mlops-image-data", "all-mlops-sequence-data"]
-}+},+{+ "name": "MLOps Image Data",+ "slug": "all-mlops-image-data",+ "incompatibleWith": ["all-mlops-tabular-data", "all-mlops-sequence-data"]+},+{+ "name": "MLOps Sequence Data",+ "slug": "all-mlops-sequence-data",+ "incompatibleWith": ["all-mlops-tabular-data", "all-mlops-image-data"]+}🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/AUTHORING.md` around lines 410 - 420, Complete the “Data path collision
(modality packs)” example in docs/AUTHORING.md by showing entries for all three
packs: all-mlops-tabular-data, all-mlops-image-data, and
all-mlops-sequence-data. Make each incompatibleWith list symmetric and include
every pairwise conflict, consistent with the one-modality-pack rule; do not
leave the block as a partial example.
| | Variable | Default | Description | | ||
| |----------|---------|-------------| | ||
| | `AI_CHAT_PROVIDER` | `mock` | Provider: `mock`, `openai`, `anthropic`, `google`, etc. | |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟠 Major | ⚡ Quick win
Document only implemented providers.
Line [56] lists openai, anthropic, and google, but the generated template describes its provider abstraction as mock-only in extensions/fastapi-ai-chat/README.md, Lines [9-10]. The service error path and extensions/fastapi-ai-chat/template/tests/test_chat.py, Lines [74-86], also treat unknown providers as failures.
Either implement and test these providers, or document mock as the only supported provider and mark the others as future placeholders.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@extensions/fastapi-ai-chat/README.md` at line 56, Update the AI_CHAT_PROVIDER
documentation in the README to list mock as the only currently supported
provider, removing unimplemented providers from the supported-values description
and optionally labeling them as future placeholders. Keep the generated template
and test behavior consistent with this documented provider scope.
ulises-jeremias
commented
Aug 16, 2026
Closing. The #151 MLOps contract link already landed in #164. The leftover files collide with #171 / #170 / #169, and a few of the route/README claims do not match the current tree (for example |
Adds reference to MLOps template contract in documentation
Summary by CodeRabbit
Documentation
Template Updates