Mason:...Mason1(3pm)

💖 Mason::Manual::UpgradingFromMason1 — a lil guide bestie 💖

Perl documentation, user contributed, and it's the Mason::Manual::UpgradingFromMason1 page, which is the whole "so you're moving from Mason 1 to Mason 2" situation. ✨

---

🌸 NAME 🌸

Mason::Manual::UpgradingFromMason1 — a summary of the differences between Mason 1 and Mason 2. iykyk 🫶

---

🦋 DESCRIPTION 🦋

okay so Mason 2.x shows up a whole ten years after Mason 1.0 (the one you know as HTML::Mason) and twelve years after the original Mason release dropped. it got rearchitected and reimplemented from the ground up, no cap 💅

that being said tho — the philosophy and the core syntax are similar enough that it should still be recognizable and still "feel like Mason" to the existing girlies. 👑

this manual is literally just trying to summarize the differences between Mason 1 and 2, so existing users can decide if they're interested and, if they are, migrate their projects. 🌈

lowkey there is currently no automated way to convert a Mason 1 site to a Mason 2 site, but hopefully someday there will be. (Contributions welcome. :)) 🥺

---

✨ ARCHITECTURE ✨

• in Mason 1, each component was an instance of a common Component class. in Mason 2, each component is its own Moose class, with a class name generated from the component path. it's giving glow-up 💅
• the main component body — the content and the inline Perl sections — gets placed into a "main" method.
• calling a component (via <& &> or $m->comp) entails creating a new instance of the component class, and calling its "main" method. component call parameters get passed to the constructor and placed in attributes. periodt.

---

🔥 MAJOR FEATURES 🔥

• plugins now utilize Moose roles and are much more powerful and flexible than in Mason 1. some features that were (or would have been) in the core of Mason 1 are now in plugins. see Mason::Manual::Plugins. 💜
• web integration in Mason 1 was centered around mod_perl and was part of the core. in Mason 2, all web integration has been split out into a companion web framework, Poet, which in turn uses PSGI to integrate with any server backend. you can also use Mason as the templating layer in popular web frameworks such as Catalyst and Dancer. there is no longer anything web-specific in the Mason core. 🫶
• subcomponents have been eliminated, replaced with class methods. bye bestie 👋
• error processing/formatting has been eliminated. Mason now simply throws fatal errors to the caller. in a Plack environment, Plack::Middleware::StackTrace will catch the error and format it nicely. slay ✨
• resolvers and anonymous components have been eliminated. components need to be in files. if your components live in another data source, you could use FUSE <http://fuse.sourceforge.net/> or a custom plugin to keep a file hierarchy up to date with the data source. 🧚
• caching support has been simplified. $m->cache simply returns a CHI object with an appropriate namespace for the component. iconic.

---

🎀 SYNTAX 🎀

• <%once> has been replaced with <%class>.
• <%cleanup> has been eliminated; it was not very useful anyway, since it was not guaranteed to run after an exception. you can use add_cleanup to add cleanup code for the end of the request, which is good enough in most cases, or you can add a "DEMOLISH" method to the component. 💀
• single blank lines between blocks are now removed, so you can space blocks out for readability without generating a ton of newlines. we love a clean output 🌸
• whitespace is required after a %-line and around the expression in a <% %> tag. this improves readability and leaves open the possibility of additional syntax. 🔥
• <%args> and <%shared> are gone. use Moose attributes instead.
• the <%ARGS> hash is gone, you can instead use $.args or $self->args to get all the parameters passed to a component. 👑
• <%method> and <%def> have been replaced with just <%method>, which creates a true class method rather than a subcomponent.
• the <%filter> tag is now used to define filters, instead of automatically applying a filter to the current component.
• "Components with content" syntax has been eliminated; use the CompCall filter instead.
• "Escape flags" in substitution tags now utilize filters.

---

🌈 MISC PARAMETER CHANGES 🌈

🌟 Interp parameters

• "buffer_preallocate_size", "code_cache_max_size" and "use_object_files" have been deemed unnecessary and eliminated.
• "escape_flags" has been eliminated; define filters instead.
• "data_dir" now defaults to a directory created with tempdir.
• "preloads" has been eliminated; this code does roughly the same:

$interp->load($_) for (grep { /some_condition/ } $interp->all_paths);

🌟 Request parameters

• "autoflush" and "max_recurse" have been eliminated because they are too difficult to implement efficiently. 😭

🌟 Compiler parameters

• "preprocess", "postprocess_perl", and "postprocess_text" have been eliminated; similar effects can be achieved with plugins targeting Mason::Compilation.
• "default_escape_flags" has been eliminated, but see Mason::Plugin::DefaultFilter for a third-party substitute. 💜

---

💅 MISC METHOD CHANGES 💅

🌟 Interp methods

• "exec" has been renamed to run.

🌟 Request methods

• "cache_self" has been eliminated; use the Cache filter instead.
• "callers", "caller" and "caller_args" have been eliminated; now that component calls are simply method calls underneath, they are too difficult to implement efficiently. 💀
• "call_next" has been replaced with Moose's "inner".
• "call_self" has been eliminated; use filters instead.
• "current_comp" has been eliminated. within a component, use $self; outside a component you can call current_comp_class, which will at least get you the class. 🫶
• "dhandler_arg" has been renamed to path_info.
• "exec" has been renamed to run.
• "fetch_comp" has been renamed to load.
• "subexec" has been replaced with visit and go.

---

🦋 SEE ALSO 🦋

Mason

---

💖 AUTHOR 💖

Jonathan Swartz <swartz@pobox.com>

---

👑 COPYRIGHT AND LICENSE 👑

this software is copyright (c) 2012 by Jonathan Swartz.

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

---

k that's the whole thing bestie!! this page came from the User Contributed Perl Documentation for perl v5.34.0, dated 2022-05-27, and it's filed under Mason:...Mason1(3pm). go forth and migrate, you got this 💅✨🌸