Skip to content

Replace Blaze with Ember (client only)#612

Open
neko-kai wants to merge 4 commits into
developfrom
experimental/http4s-ember-client-only
Open

Replace Blaze with Ember (client only)#612
neko-kai wants to merge 4 commits into
developfrom
experimental/http4s-ember-client-only

Conversation

@neko-kai
Copy link
Copy Markdown
Member

No description provided.

Caparow and others added 4 commits July 18, 2024 15:58
Resurrects 135a9f9 on top of develop and bumps http4s to 0.23.34
(latest 0.23.x stable; ignoring the 1.0-Mx milestones). Two newer
test artifacts (McpBridgeRealServerSpec, mcpdemo.McpDemoMain) that
post-date the original commit are also ported from Blaze to Ember.

build.sbt regenerated via ./sbtgen.sc --js.
…mber.

Replaces the original 135a9f9 contents with the resurrected, modernized
version (http4s/ember 0.23.34, sbtgen-based build, ports for the
McpBridgeRealServerSpec and mcpdemo.McpDemoMain tests added after
135a9f9). Recorded as a merge so the existing upstream PR ref can be
fast-forwarded without `--force`.
`HttpRpcDispatcherFactory` keeps `EmberClientBuilder` from the
previous commit. Server-side users (Http4sTransportTest, the
McpBridgeRealServerSpec real socket, and the mcpdemo runner) move
back to `BlazeServerBuilder` — the WS websocket app is still
served from Blaze (`http4s-blaze-server` 0.23.17, the last
available 0.23.x release). `http4s-ember-server` is dropped from
the runtime-rpc-http4s deps.

build.sbt regenerated via ./sbtgen.sc --js.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants