https://discord.cloudflare.com logo
Join Discord
Powered by
# workers-discussions
  • m
    I'm returning too many embeds for a single response
  • g
    Ah, gotcha
  • m
  • g
    Nice! Disgusting. But nice 😉
  • m
  • a
  • a
    the hell is this
  • a
    Can the slash command return messages before the response? Or does that change how the actual response is interpreted?
  • m
    Yeah, you can return messages before you respond. All that happens is that in the Discord client, your messages appear before the 'user used /whatever' message
  • a
    Maybe that'd be better in this case? The code would be easier to read and understand and you could easily see who called the bot without having to scroll to the top of the response.
  • a
    Just my $0.02
  • m
    Yeah, potentially. It'd just be deciding at what point to send the ack after the messages. For a single record-type response, imo it'd look weird to send the single embed and then the ack
  • m
    Maybe just at 10+ record types, when this logic kicks in
  • a
    hmm
  • a
    has anyone actually tried sending follow-ups before responding
  • m
    Yes
  • m
    I have
  • j
    hahahaha @User you are everywhere
  • a
    interesting
  • a
    i wonder if that was intended to work
  • a

    https://advaith.is-in-hyper.space/43d92deac6.pngâ–¾

  • j
    huh
  • m
    It certainly feels odd that it works
  • m
    But ¯\_(ツ)_/¯
  • a
    feature not a bug :D
  • m
    Is it safe to fire-and-forget writes to KV from a Worker or do you risk the task being cancelled like when you fire-and-forget a fetch.
  • g
    The latter. Can say from experience.
  • g
    You should definitely await it, (either with 
    waitUntil
    and hope that succeeds, or ideally in your 
    respondWith
    )
  • m
    Thanks!
  • s
    Hello, is there any way to make cloudflare serverless workers work with WebSockets?
1...525354...2509Latest