From 73c8c6b361d74401fddb66068d4ddc5f8c797fa3 Mon Sep 17 00:00:00 2001 From: Filip Hoffmann Date: Tue, 5 May 2026 01:41:26 +0200 Subject: [PATCH] personal rant --- examples/http_interactions/README.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/examples/http_interactions/README.md b/examples/http_interactions/README.md index 8d2e24f..a9b4cc2 100644 --- a/examples/http_interactions/README.md +++ b/examples/http_interactions/README.md @@ -29,6 +29,19 @@ This is useful for serverless setups where the only event you handle is `INTERAC Right now, in grom, it is the only way to use interactions, seeing as the gateway is in a broken state. +
+Why so much boilerplate in the code? (personal rant) +Well, it all comes down to: grom is kind of bad right now. + +I originally wanted to write a plug-in wisp middleware, but that would require grom to import wisp. + +I could create a new project for this, but I'd then miss out on all the decoders/encoders, and interactions use **lots** of them. + +So, a compromise is to only deal with gleam_http primitives and interactions in grom, and leave all the handling to the user. + +This will be improved in the grom rewrite, where everything will be much more modular. +
+ ## How? We're going to use wisp to create a webhook handler, register it with Discord, and hopefully have HTTP interactions working by the end of the night. -- 2.51.2