GOLF(2gg)

💖 GOLF(2gg) — after-handler 💖

okay bestie, welcome to the Golf manual, section 2gg, and this one is literally the after-party of your request lifecycle. no cap. 🎀

---

✨ NAME ✨

after-handler — it's giving (service-processing) 🦋

---

🌸 PURPOSE 🌸

Run your code after a request gets handled. that's it, that's the whole vibe. periodt. 💅

---

⭐ SYNTAX ⭐

after-handler
...
end-after-handler

---

👑 DESCRIPTION 👑

so here's the tea, bestie 🫖 — every single Golf request rolls through a request dispatcher (go peek at request(), iykyk). and if you wanna say "hey, run my code after a request is handled", you do it like this:

• make a source file called after-handler.golf 📁
• implement a handler that starts with after-handler and ends with end-after-handler
• and boom 💥 — it gets automatically picked up and compiled with your application. no wiring, no setup, it just knows. main character energy fr fr.

now for the fine print, and this part matters:

if no request executes — like, say your app just doesn't handle a given request — then the after-handler handler does not execute either. sad but true 😭

BUT 🚨 if you use exit-handler to exit the current request handling, the after-handler handler still executes. the after-party goes on, babe. 🔥

---

🌈 EXAMPLES 🌈

here's a lil baby implementation of an after-handler handler that just outputs "Hi there!!" — adorable, iconic, no notes ✨:

after-handler
     @Hi there!!
end-after-handler

---

🧚 SEE ALSO 🧚

• Service processing 💜
• after-handler
• before-handler
• begin-handler
• call-handler
• See all documentation 📚

---

and that's a wrap on GOLF(2gg), bestie!! this page was served up by $VERSION, dated $DATE — go forth and handle your requests after everything else, slay 💅✨🫶