| 123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081 |
- """Pydantic schemas for the unified slicer-presets endpoint.
- The SliceModal pulls printer/process/filament options from three sources, in
- priority order: cloud (the user's Bambu Cloud account), local (DB-backed
- imported profiles), and standard (slicer-bundled stock profiles). The endpoint
- returns all three lists with name-based dedup applied so each preset appears
- exactly once across the response.
- """
- from typing import Literal
- from pydantic import BaseModel
- CloudStatus = Literal["ok", "not_authenticated", "expired", "unreachable"]
- class UnifiedPreset(BaseModel):
- """A single printer/process/filament preset with its source.
- The ``id`` shape varies by source:
- - cloud → Bambu Cloud setting_id (e.g. ``"PFUS9ac902733670a9"``)
- - local → stringified DB row id from ``local_presets``
- - standard → preset name as written in the bundled JSON (the slicer
- resolves bundled profiles by name during inheritance walk)
- The frontend treats ``id`` as opaque; the slice dispatch path uses
- ``(source, id)`` to fetch / pass the preset content to the sidecar.
- ``filament_type`` and ``filament_colour`` are populated for the filament
- slot only — they let the SliceModal pre-pick a preset per plate slot in
- the multi-color flow by matching against the source 3MF's per-slot type
- and color. Populated when the underlying preset JSON exposes them; left
- as ``None`` on bundled profiles where colour is a runtime spool attribute.
- ``compatible_printers`` is the slicer's own list of printer-preset names a
- process / filament preset declares itself valid for. Populated for the
- local tier (stored at import time); left ``None`` for cloud (no per-preset
- detail is fetched — rate limits) and standard (the sidecar's bundled
- listing doesn't expose it). The SliceModal uses it to filter the
- process / filament dropdowns by the selected printer (#1325); when it is
- ``None`` the modal falls back to the user's uploaded Slicer Bundles, which
- map each printer to the presets it ships.
- """
- id: str
- name: str
- source: Literal["orca_cloud", "cloud", "local", "standard"]
- filament_type: str | None = None
- filament_colour: str | None = None
- compatible_printers: list[str] | None = None
- class UnifiedPresetsBySlot(BaseModel):
- """Three slots in the order Bambu Studio / OrcaSlicer use."""
- printer: list[UnifiedPreset] = []
- process: list[UnifiedPreset] = []
- filament: list[UnifiedPreset] = []
- class UnifiedPresetsResponse(BaseModel):
- """Each tier carries only the names that didn't appear in a higher tier.
- Priority order: ``orca_cloud > cloud > local > standard``. Orca Cloud is
- highest because it's the most-recently-explicitly-curated source for
- users who set up Orca sync (they did it on purpose; their Orca picks
- should outrank everything else). Bambu Cloud follows as the next-most-
- curated tier. Local imports beat the slicer's stock fallback.
- ``cloud_status`` / ``orca_cloud_status`` let the frontend show a banner
- explaining why a cloud tier is empty when the user expected to see it
- (signed out / token expired / network down). Each tier has its own
- status because they can fail independently.
- """
- orca_cloud: UnifiedPresetsBySlot = UnifiedPresetsBySlot()
- cloud: UnifiedPresetsBySlot = UnifiedPresetsBySlot()
- local: UnifiedPresetsBySlot = UnifiedPresetsBySlot()
- standard: UnifiedPresetsBySlot = UnifiedPresetsBySlot()
- cloud_status: CloudStatus = "ok"
- orca_cloud_status: CloudStatus = "ok"
|
