XMLSpecListSpec(3pm)

📦 version 2.1.1, in arch rolling

💅 XMLSpecListSpec(3pm) — the vibes are very Lire::Config, bestie

okay so real quick, this is a page from LogReport's Lire Documentation (yes, that Lire — the 3pm perl module situation). Buckle up, it's a short one but it's lowkey iconic 🎀

✨ NAME ✨

Lire::Config::XMLSpecListSpec — literally just a list of XML specifications. that's it. that's the whole vibe. 🌸

🦋 DESCRIPTION 🦋

So Lire::Config::TypeSpec already has a thing called ListSpec, right? Well this class? This class defines a special kind of ListSpec. Not like other girls 💅

The way it works: it overrides the has_component(), get(), component_names() and components() methods so that every XML report specification or filter specification is available. And the gag is — these specifications are created dynamically at runtime. not pre-baked, not sitting in a config file somewhere. born fresh, main character energy ✨

🎀 new( 'name' => $name, 'type' => 'filters'|'reports )

Creates a new Lire::Config::XMLSpecListSpec object which will contain a list of report or filter specifications configuration. 🫶

The type parameter is what decides whether a Lire::ReportSpec or a Lire::FilterSpec will be created — so like, pick your fighter. (yes the original docs spell it "creatd", we're all doing our best here 😭)

new( 'name' => $name, 'type' => 'filters'|'reports )

🧚 type()

Returns the type of specification contained by this object. literally just tells you what's inside. no cap. ⭐

💜 has_component( $name )

This spec returns true when $name is of the form superservice:id — and only if there's actually an available id specification defined in superservice. 💖

Otherwise? It returns false. Sorry bestie, that's the whole rule. 🙈

🌈 component_names()

Returns an array containing the configuration name of all available specifications. every single one. the whole roster. 👑

🔥 get( $name )

Returns an Lire::Config::ObjectSpec specification for the component named $name.

And this ObjectSpec is the one that will instantiate a Lire::ReportSpec or a Lire::FilterSpec of the appropriate type. so it's giving "middle management but make it useful" 💀

🌟 components()

Returns an array containing all the Lire::Config::ObjectSpec defining the available specifications. yes, all of them. glutinous. we love to see it. 🍓

👀 SEE ALSO 👀

go read those too, iykyk 🦋

📌 VERSION 📌

$Id: XMLSpecListSpec.pm,v 1.8 2006/07/23 13:16:31 vanbaal Exp $

💌 AUTHOR 💌

Francis J. Lacoste <flacoste@logreport.org> — thank you for your service, king 🫶

Copyright (C) 2004 Stichting LogReport Foundation LogReport@LogReport.org

This file is part of Lire.

Lire is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. 💖

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Please see the GNU General Public License for more details. ⚠️ (like fr fr, no promises, read the license)

You should have received a copy of the GNU General Public License along with this program (see COPYING); if not, check with http://www.gnu.org/copyleft/gpl.html. 🎀

okay and that's the whole page!! this was Lire 2.1.1, dated 2025-09-28 — periodt, we're done here 💅✨ 🦋

📦 where this page comes from