SVK::Lo...ipeline(3)

💖 SVK::Log::FilterPipeline 💖

okay bestie, so this page is from the User Contributed Perl Documentation, and it's all about SVK::Log::FilterPipeline, which is genuinely such a vibe once you get it. it's giving "assembly line but for log filters". let's go 💅

---

✨ NAME ✨

SVK::Log::FilterPipeline — a pipeline of log filter objects 🎀

---

🌸 DESCRIPTION 🌸

so an SVK::Log::FilterPipeline represents a particular collection of log filter objects, and like… each one of them needs to be called in turn. that's it. that's the whole thing. it's a squad of filters that take turns doing their lil jobs, in order, no skipping, no cutting the line. 💖

---

🦋 METHODS 🦋

⭐ new ⭐

Construct a new SVK::Log::FilterPipeline object by constructing the specific filters that will handle the details and preparing for the first revision. ✨

so yeah, new is the glow-up moment — it builds the actual filter objects, gets everything set up, and gets ready for revision number one. main character energy fr. 👑

---

⭐ build_filter_object ⭐

Given the name of a filter, try and construct an appropriate filter object. Search @INC for modules that match the name given. If no appropriate classes are available, we die with an appropriate warning. 💀

This method creates an object for the filter by calling its new() method.

ngl if the module isn't in @INC it's not ghosting you, it literally does not exist, and this method will die about it. rip. 😭

---

⭐ filter ⭐

SVK::Command::Log calls this routine when it wants to display (or process) a revision. The method then dispatches the information to the methods of the necessary filter objects in the pipeline to perform the real work. 🫶

like, filter is the manager. SVK::Command::Log walks in like "hey we got a revision", and filter is like "say less" and hands the actual work off to whoever in the pipeline is supposed to handle it. delegation queen. 💅

---

⭐ finished ⭐

Tell all the filters that their jobs are done by calling "footer" and "teardown" on each one. 🌈

wrapping up, closing the group chat, saying goodnight — "footer" and "teardown" on every single filter. periodt. ✨

---

⭐ get_pipeline_command ⭐

Examine an exception to determine if it's a pipeline control exception. If it is, return the desired pipeline command. If it's not, rethrow the exception. If no exception is provided, the command 'continue' is returned. 🧚

so it's doing a lil vibe check on the exception: pipeline control? cool, hand back the command. not pipeline control? nope, rethrown, not our problem bestie. and if you hand it nothing at all, it just says 'continue' and moves on. lowkey the chillest method here. 💜

---

⭐ present_revision ⭐

Display a single revision by passing it to the pipeline's presentation filter. 🌸

one revision, one presentation filter, one job. slay. 💖

---

⭐ run_pipeline ⭐

Send a revision down the pipeline. Provide revision information to the revision() method of each filter in the pipeline until one of them says to stop. Then return the pipeline command. 🔥

so the revision travels down the line, hitting revision() on each filter in turn, and the moment one of them is like "okay stop", we stop. then the pipeline command comes back out the other end. it's giving relay race, honestly. 🎀

---

⭐ set_up_presentation ⭐

Handle initial set up for the presentation filter. This should only be called once during an SVK::Log::FilterPipeline's lifetime. ⚠️

fr fr, once in the lifetime. not twice. don't be that person. 🙈

---

⭐ set_up_selection ⭐

Handle initial set up for the selection filter pipeline. This should only be called once during "SVK::Log::FilterPipeline"'s lifetime. ⚠️

same deal as above but for the selection filter pipeline — initial set up, and again, literally only once ever during the object's whole lifetime. 💀

---

⭐ split_filter ⭐

Split a string into a filter name and an arbitrary argument string. ✂️

name over here, arbitrary args over there. clean split, no mess, no drama. 💅

---

⭐ split_selectors ⭐

Split the description of the selection filter pipeline into individual filter names and their arguments. Each filter is separated by a '|' character. Literal pipe characters are included with '\|'. 🦋

okay this one's important, so listen up bestie:

• filters are separated by '|'
• if you want an actual literal pipe character, you escape it with '\|'

so '|' is the divider, '\|' is the "no bestie this one is a real pipe, don't split here" signal. iykyk. ✨

---

and that's the whole page!! no cap, you now know the entire SVK::Log::FilterPipeline lore 💖

this was perl v5.42.0, dated 2025-07-25, from the SVK::Lo...ipeline(3) page of the User Contributed Perl Documentation. mwah, go build a pipeline, you got this 🫶✨🎀