Alien:...figData(3pm)

πŸ“¦
version 0.09 Β· 2 versions
, in fedora 43

πŸ’– NAME πŸ’–

Alien::ProtoBuf::ConfigData β€” bestie, this is literally the configuration vault for Alien::ProtoBuf. That's it. That's the whole vibe. πŸŽ€


✨ SYNOPSIS ✨

okay so here's how you actually talk to it:

use Alien::ProtoBuf::ConfigData;
$value = Alien::ProtoBuf::ConfigData->config('foo');
$value = Alien::ProtoBuf::ConfigData->feature('bar');

@names = Alien::ProtoBuf::ConfigData->config_names;
@names = Alien::ProtoBuf::ConfigData->feature_names;

Alien::ProtoBuf::ConfigData->set_config(foo => $new_value);
Alien::ProtoBuf::ConfigData->set_feature(bar => $new_value);
Alien::ProtoBuf::ConfigData->write;  # Save changes

like. it's giving "I hold the config AND I let you poke at it." main character energy fr fr πŸ’…


πŸ¦‹ DESCRIPTION πŸ¦‹

So Alien::ProtoBuf::ConfigData is the little module that holds all the configuration data for the Alien::ProtoBuf module. 🫢 But it's not just a storage locker β€” it also hands you a whole programmatic interface for getting or setting that configuration data. So you can read it, you can write it, you can do the most.

⚠️ but listen. to actually make changes, you have to have write access to the Alien::ProtoBuf::ConfigData module. and you should attempt to understand the repercussions of your actions. that's the original wording and honestly? iconic. don't just start setting stuff, bestie. know what you're doing first. πŸ™ˆ

πŸ‘‘ METHODS πŸ‘‘

🌸 config($name)

Give it a string argument and it returns the value of the configuration item with that name. if there's no such item? you get undef. no item, no value, no drama. πŸ’€

🌸 feature($name)

Same energy, but for features: give it a string, get back the value of the feature by that name. no such feature? undef again. ✨

🌸 set_config($name, $value)

Sets the configuration item with the given name to the given value. and the value can be any Perl scalar that will serialize correctly using Data::Dumper β€” so yes, references, objects (usually), and complex data structures all count. πŸŽ€

it probably does not include transient things like filehandles or sockets though. so don't try it. nope.

🌸 set_feature($name, $value)

Sets the feature with the given name to the given boolean value. it'll get converted to 0 or 1 automatically. no cap, it just does that. πŸ’…

🌸 config_names()

Returns a list of all the names of config items currently defined in Alien::ProtoBuf::ConfigData. in scalar context? you get the number of items instead. list or count, pick your fighter. πŸ”₯

🌸 feature_names()

Returns a list of all the names of features currently defined in Alien::ProtoBuf::ConfigData, or in scalar context the number of features. same deal as above. ⭐

🌸 auto_feature_names()

Returns a list of all the names of features whose availability is dynamically determined, or in scalar context the number of such features.

heads up bestie: it does not include features that have later been set to a fixed value. so once you've locked one down, it's out of this list. 🧚

🌸 write()

Commits any changes from set_config() and set_feature() to disk. πŸ“ requires write access to the Alien::ProtoBuf::ConfigData module. that's the whole point. save your work, queen. πŸ’–


πŸ’œ AUTHOR πŸ’œ

Alien::ProtoBuf::ConfigData was automatically created using Module::Build. and Module::Build was written by Ken Williams β€” but he holds no authorship claim or copyright claim to the contents of Alien::ProtoBuf::ConfigData. so like, credit where it's due but also not where it isn't. periodt. πŸ‘‘


and that's the whole page, bestie 🫢 this was pulled straight from the User Contributed Perl Documentation, riding along with perl v5.42.0, dated 2025-07-25. go forth and configure responsibly πŸ’…βœ¨πŸ“

πŸ“¦ where this page comes from