Bio::A...anager(3pm)

💖 Bio::Annotation::TypeManager — the vibe manager for annotation types 💖

okay bestie, so this is Bio::Annotation::TypeManager(3pm), and it lives in the User Contributed Perl Documentation corner of the perl universe (iykyk). It's a Bioperl module, and no cap it does exactly what the name says: it manages types for annotation collections. That's the whole assignment. She's focused, she's iconic, she's not doing extra credit. 💅

---

✨ NAME ✨

Bio::Annotation::TypeManager — Manages types for annotation collections 🎀

---

✨ SYNOPSIS ✨

okay so here's the whole flex, fr fr:

    # default type manager

    $tm = Bio::Annotation::TypeManager->new();

    # $key is a string or a Bio::Ontology::TermI compliant object
    print "The type for $key is ",$tm->type_for_key($key),"\n";

    if( !$tm->is_valid($key,$object) ) {
        $self->throw("Invalid object for key $key");
    }

like… make a default type manager, ask it what the type is for your $key (which can be a plain string or a Bio::Ontology::TermI compliant object, periodt), and if the thing you passed in isn't valid for that key, $self->throw goes off. main character energy, honestly. 😭

---

✨ DESCRIPTION ✨

Manages types for annotation collections.

that's it. that's the description. short, sweet, to the point, a queen of economy. 🫶

---

✨ FEEDBACK ✨

🌸 Mailing Lists 🌸

User feedback is an integral part of the evolution of this and other Bioperl modules. bestie, they are literally asking for your thoughts. Send your comments and suggestions preferably to one of the Bioperl mailing lists. Your participation is much appreciated. 🦋

  bioperl-l@bioperl.org

🌸 Support 🌸

Please direct usage questions or support issues to the mailing list:

bioperl-l@bioperl.org

rather than to the module maintainer directly. no fr, don't DM the maintainer, the group chat is right there. Many experienced and reponsive experts will be able look at the problem and quickly address it. Please include a thorough description of the problem with code and data examples if at all possible — receipts, bestie, we need the receipts. 💀

🌸 Reporting Bugs 🌸

Report bugs to the Bioperl bug tracking system to help us keep track the bugs and their resolution. Bug reports can be submitted via the web:

  https://github.com/bioperl/bioperl-live/issues

---

✨ AUTHOR - Ewan Birney ✨

Email birney@ebi.ac.uk 👑

---

✨ APPENDIX ✨

The rest of the documentation details each of the object methods. Internal methods are usually preceded with a _ — so if it starts with an underscore, that's her private little corner, mind ya business (but also here's the docs anyway, we're transparent like that). 🧚

💜 new

Title   : new
Usage   :
Function:
Example :
Returns :
Args    :

no usage, no function, no example, no returns, no args listed — she said "mystery" and honestly? respect. ✨

💜 type_for_key

Title   : type_for_key
Usage   :
Function:
Example :
Returns :
Args    :

same deal — the title is all we get. but the SYNOPSIS told you the tea: you hand it a $key (a string or a Bio::Ontology::TermI compliant object) and it hands back the type. 🍓

💜 is_valid

Title   : is_valid
Usage   :
Function:
Example :
Returns :
Args    :

also just vibes and a title. but again, the SYNOPSIS spills: $tm->is_valid($key,$object) tells you whether that $object is actually valid for that $key. if it's not… throw. 😭

💜 _add_type_map

Title   : _add_type_map
Usage   :
Function:
Example :
Returns :
Args    :

underscore alert 🚨 so this is one of the internal ones. title only, as is tradition around here. 🙈

---

ok that's the whole page bestie, every option, every method, every email, every link, nothing skipped, we ate and left no crumbs 🔥

---

and finally, the cute lil sign-off: this page is from perl v5.32.1, dated 2021-08-15, and it's filed under Bio::A...anager(3pm) 💖 slay, go annotate something 🌈⭐