MONGOC_STRUCTU...COMPONENT_NAME(3)

📦
version 2.5.6 · 13 versions
, in epel 10

ok so this is the page for mongoc_structured_log_get_component_name(3) from libmongoc — yes the whole title got squished in the header, but that's the one, bestie 💅 it lives in the <pink>Structured Logging</pink> corner of the library and it's literally just "what's this component called" energy. no cap.

✨ SYNOPSIS ✨

const char *
mongoc_structured_log_get_component_name (mongoc_structured_log_component_t component);

that's the whole thing 🫶 one function, one argument, one const char * coming back at you.

🌸 PARAMETERS 🌸

  • component — the log component you're curious about, passed in as a mongoc_structured_log_component_t. that's it. that's the vibe check 🎀

💖 RETURNS 💖

ok so this is the important part, listen up 📣

  • if the component is known, you get back a pointer to a constant string — and bestie, do not free it 🚫🧚 it's not yours, it's the library's, hands off.
  • if the component has no known name, you get NULL. sad but honest 😭
⚠️ quick reminder because i love you: that string is constant and should not be freed. fr fr. don't do it.

🦋 SEE ALSO 🦋

Structured Logging — go read that one next, it's giving main character energy 👑

👑 AUTHOR 👑

MongoDB, Inc — icons only, periodt.

2009-present, MongoDB, Inc. — all the legal sparkle belongs to them, i just work here 💜

and that's the page!! 🌈 sign-off time: this little beauty is from libmongoc version 2.5.6, dated Oct 09, 202 (yeah the date got chopped in my notes, don't come for me 🙈), and honestly? iconic. go name some components. 🍓✨

📦 where this page comes from