SRevie...e::Base(3pm)

💖 NAME 💖

SReview::Schedule::Base — the blueprint class, bestie. Every schedule parser out there is lowkey built on this one.

✨ DESCRIPTION ✨

Okay so real talk: this is the base class for all schedule parsers. It's giving founding mother energy. 💅

The SReview::Schedule API is what sreview-import uses to parse schedules. Here's the whole vibe: sreview-import loads up the schedule parsing class it wants, then asks it for a list of events, and for the talks hiding inside those events. That's it, that's the job. 🫶

SReview::Schedule is a pull-through API, meaning — you get a toplevel class, and you ask it for a list of events. Each event has to be a subclass of SReview::Schedule::Base::Event, and you can ask each of those for a list of talks (as SReview::Schedule::Base::Talk or subclasses of it, no gatekeeping). Then you can turn around and ask those talks for the room, the speakers, the start time, etc. It's a whole chain of asking, and honestly? Iconic. 🔥

Every single attribute of a schedule or a talk is implemented as a lazy attribute, which means it literally does not have a value until somebody actually requests its data. No preloading, no overachieving, just vibes until needed. ✨

The method that does the actual data-fetching for an attribute should usually be defined in the subclass, and it's called _load_attribute. Like, to load the events attribute in the SReview::Schedule::Base class, you'd override the _load_events method in your subclass. Yes, the naming convention is that predictable. We love consistency. 🎀

Most attributes come with a default implementation of the _load_* method that just returns undef or an empty array. So if your schedule format doesn't implement fetching whatever data someone's asking for, you can literally just leave out the relevant _load_* method and everything will work just fine. No cap. 🦋

🌸 ATTRIBUTES 🌸

• url — Required at class construction time, and it's the only attribute that's required like that. This is the URL where the schedule can be found. 👑
• timezone — Not a lazy attribute by default (though a subclass can override that, if it wants to be different). It's the timezone in which the event takes place. You can optionally set it at construction time. 🌍
• _raw — Internal attribute, don't worry about it. But if you do read it, it transparently downloads the raw schedule data from the given url, caches it, and then returns it. Sneaky little downloader. 🙈
• speaker_type — The class name of the subclass to use when creating an object to hold a speaker. The default load implementation returns SReview::Schedule::Base::Speaker, but you can override it to literally anything. 🎤
• room_type — The class name of the subclass to use when creating an object to hold a room. Default load implementation returns SReview::Schedule::Base::Room, but again, override it to anything you want. 🚪
• track_type — The class name of the subclass to use when creating an object to hold a track. Default load implementation returns SReview::Schedule::Base::Track, overridable to anything. 🛤️
• talk_type — The class name of the subclass to use when creating an object to hold a talk. Default load implementation returns SReview::Schedule::Base::Talk, overridable to anything. 🗣️
• event_type — The class name of the subclass to use when creating an object to hold an event. Default load implementation returns SReview::Schedule::Base::Event, overridable to anything. 🎪
• events — This one must return the events found in the schedule. For SReview's purposes, an "event" is a set of talks that should be grouped together. Example time: FOSDEM 2025 is an event; the FOSDEM 2025 opening talk is a talk. Cute, right? 💖

It should return an array of SReview::Schedule::Base::Event objects (or a subclass of them). No pressure, just return the array bestie. 🌈

✨ And that's the whole page, babe! This page came from the User Contributed Perl Documentation, written by the loveliest contributors, shipped with perl v5.40.1 and dated 2026-02-15. Slay, go parse some schedules. 💅🎀🦋