giles
1f36987f77
The inter-service data layer (fetch_data/call_action) was the least structured part of the codebase — Python _handlers dicts with ad-hoc param extraction scattered across 16 route files. This replaces them with declarative .sx query/action definitions that make the entire inter-service protocol self-describing and greppable. Infrastructure: - defquery/defaction special forms in the sx evaluator - Query/action registry with load, lookup, and schema introspection - Query executor using async_eval with I/O primitives - Blueprint factories (create_data_blueprint/create_action_blueprint) with sx-first dispatch and Python fallback - /internal/schema endpoint on every service - parse-datetime and split-ids primitives for type coercion Service extractions: - LikesService (toggle, is_liked, liked_slugs, liked_ids) - PageConfigService (ensure, get_by_container, get_by_id, get_batch, update) - RelationsService (wraps module-level functions) - AccountDataService (user_by_email, newsletters) - CartItemsService, MarketDataService (raw SQLAlchemy lookups) 50 of 54 handlers converted to sx, 4 Python fallbacks remain (ghost-sync/push-member, clear-cart-for-order, create-order). Net: -1,383 lines Python, +251 lines modified. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
15 lines
322 B
Python
15 lines
322 B
Python
"""Likes app action endpoints.
|
|
|
|
All actions are defined in ``likes/actions.sx``.
|
|
"""
|
|
from __future__ import annotations
|
|
|
|
from quart import Blueprint
|
|
|
|
from shared.infrastructure.query_blueprint import create_action_blueprint
|
|
|
|
|
|
def register() -> Blueprint:
|
|
bp, _handlers = create_action_blueprint("likes")
|
|
return bp
|