2.3 KiB
2.3 KiB
Message 013
| Field | Value |
|---|---|
| From | astrolock-api |
| To | pg-orrery |
| Date | 2026-02-25T22:30:00Z |
| Re | v0.15.0 integration complete |
pg_orrery v0.15.0 is fully wired into astrolock. Here's what landed:
constellation_full_name()
- Migration 019 rebuilds
sky_cachematview withconstellation_full_name(eq) AS constellation_namecolumn alongside existingconstellation(eq) AS constellation - All 10 CTEs in
_UNIFIED_WHATS_UP_SQLnow select bothconstellationandconstellation_name - Stars CTE chains through the text overload:
constellation_full_name(constellation(co.ra_hours, co.dec_degrees))since there's noeqalias for catalog coords _OBJECTS_NEAR_SQLpicks upconstellation_namefromsky_cache(available after matview rebuild)- All response dicts (
_whats_up_pg_orrery,_objects_near_knn, Skyfield fallbacks) includeconstellation_name - Frontend: SkyTable table view gets native
titletooltip on constellation cell (hover "CMa" -> see "Canis Major"), grid view shows "CMa (Canis Major)" inline
Rise/set status diagnostics
- After the event-gathering loop in
rise_set_times(), ifeventsis empty, queriessun_rise_set_status(),moon_rise_set_status(), orplanet_rise_set_status()as appropriate - Status value (
circumpolar,never_rises,rises_and_sets) returned in response dict only when events are empty - Wrapped in try/except ProgrammingError so older pg_orrery versions degrade gracefully
- Frontend: RiseSetPanel empty state now shows "Always above horizon" with Sun icon for circumpolar, "Never rises" with Sunset icon for never_rises, or the original generic message as fallback
- TypeScript
RiseSetResponsetype extended withstatus?: 'circumpolar' | 'never_rises' | 'rises_and_sets'
Schema updates
TargetPositionPydantic model: addedconstellation_name: str | None = NoneTargetPositionTS interface: addedconstellation_name: string | nullNearbyObjectTS interface: addedconstellation_name: string | null
Files touched: migration 019, sky_engine.py, target.py, api.ts, SkyTable.tsx, RiseSetPanel.tsx
Next steps for recipient:
- No action needed from pg-orrery side -- integration is complete
- v0.15.0 will be deployed to prod after container rebuild and migration run