Bread:...Manual(3pm)

✨ NAME ✨

okay bestie, welcome to Bread::Board::Manual — the whole entire manual for Bread::Board 💖 (this is a Bread:...Manual(3pm) situation, from the User Contributed Perl Documentation collection, in case you were wondering which shelf it lives on 🎀)

---

🌸 VERSION 🌸

this is version 0.37, no cap 🫶

---

💅 INTRODUCTION 💅

so, like we already said: Bread::Board is an inversion of control framework, and its whole personality is dependency injection plus lifecycle management. the goal it's striving towards? promoting more decoupled designs. how? by literally removing the need for your objects to be concerned with resolving and/or creating their own dependencies — and also removing any need for them to know (or care 😌) what their lifecycle is.

🦋 Why should I use Bread::Board 🦋

first things first, bestie: Bread::Board and IoC are not universally useful. smaller applications and one-off scripts would be straight-up overburdened by the abstractions of Bread::Board. but the larger your application becomes, the more something like Bread::Board can help you out. it's giving glow-up for big codebases 💅

as applications grow, so does the burden of managing resources and their dependencies. making sure all your components are properly initialized, in the right order, and at all times that you actually need them? that can become a twisty maze 😭 and Bread::Board is intended to help you manage this twisty maze and remove the need for you to manage it manually. periodt.

take your typical Catalyst application — the Catalyst framework itself contains its own mini IoC framework through the component subsystem. Catalyst will manage your models and views, making sure they'll be available when you need them in the controllers. Catalyst makes all this easy to manage through its configuration system. and that's great inside your Catalyst application, but what about outside of it?? 🙈 any sufficiently complex web application will have a set of scripts and/or command-line applications to help support it. and at that point you're left to your own devices and must manage these components and their dependency chains on your own. not the vibe.

by decoupling IoC into its own stand-alone subsystem, it becomes possible to get that same ease-of-use you get inside something like a Catalyst application — but outside of it. iconic. ✨

this, in a nutshell, is what Bread::Board aims to provide. 🥜

---

🌈 SECTIONS 🌈

• Bread::Board::Manual::Concepts — this is perhaps the best place to start, bestie. it'll introduce you to the basic concepts that make up Bread::Board. main character energy, start here 💖
• Bread::Board::Manual::Concepts::Typemap — with Bread::Board you provide names for your service so that you can find them later. this document explores the new (read: experimental) typemap feature, which allows you to map services to types as well 👑
• Bread::Board::Manual::Concepts::Advanced — Bread::Board is an extensible and open system, and this document will explore how you can extend Bread::Board and get greater re-use of your components 🧚
• Bread::Board::Manual::Example — this is a set of examples meant to show how Bread::Board can be used in real-world scenarios. it is recommended that you read the above documentation first, because many of these examples use the concepts discussed in them 🍓

---

💜 AUTHOR 💜

Stevan Little <stevan@iinteractive.com> — yes, the legend themselves 😌

---

💀 BUGS 💀

please report any bugs or feature requests on the bugtracker website:

https://github.com/stevan/BreadBoard/issues

when submitting a bug or request, please include a test-file or a patch to an existing test-file that illustrates the bug or desired feature. fr fr, it helps so much 🫶

---

🎀 COPYRIGHT AND LICENSE 🎀

this software is copyright (c) 2019, 2017, 2016, 2015, 2014, 2013, 2011, 2009 by Infinity Interactive.

this is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself. slay 💅

---

and that's the whole manual, bestie!! this page was brought to you by perl v5.36.0 on 2022-12-12 🦋✨ ily, go build something decoupled 💖