The current HTTP API in /api/sky.ts is provisional; what should happen if window.ship has a value? Should all HTTP requests go to the ship? What happens there?
I think the %sky agent should handle all HTTP requests to our own namespace if we're using it from an Urbit ship. Maybe requests to other namespaces can fall back to our ship if 1) we're using Sky from an Urbit ship or 2) we're using Sky from urbit.org, but Athens knows we have a ship running.
The Sky frontend currently has the @urbit/http-api package installed, but I suspect what we want to do is send normal HTTP requests to the %sky agent via Eyre so the interaction is uniform whether Sky is talking to Urbit, Athens, or an Azimuth app.
Issue will be closed when have a stub %sky agent and /api/sky.ts we're happy with.
The current HTTP API in
/api/sky.tsis provisional; what should happen ifwindow.shiphas a value? Should all HTTP requests go to the ship? What happens there?I think the %sky agent should handle all HTTP requests to our own namespace if we're using it from an Urbit ship. Maybe requests to other namespaces can fall back to our ship if 1) we're using Sky from an Urbit ship or 2) we're using Sky from urbit.org, but Athens knows we have a ship running.
The Sky frontend currently has the
@urbit/http-apipackage installed, but I suspect what we want to do is send normal HTTP requests to the %sky agent via Eyre so the interaction is uniform whether Sky is talking to Urbit, Athens, or an Azimuth app.Issue will be closed when have a stub %sky agent and
/api/sky.tswe're happy with.