jwt_value_t(3)

💖 NAME 💖

jwt_value_t — bestie, this is the data type for all your get and set actions on JWT headers and claims 🎀

---

✨ SYNOPSIS ✨

🦋 Data Fields

jwt_value_type_t type
const char * name
union {
   jwt_long_t int_val
   const char * str_val
   int bool_val
   char * json_val
};
int replace
int pretty
jwt_value_error_t error

---

🌸 Detailed Description 🌸

Okay so, jwt_value_t is literally the data type for get and set actions on JWT headers and claims. She does both jobs 💅

You use this same struct for both set requests and get requests, and the specific rules for each type are described in more detail for the set and get requests. iykyk 👑

Note 📌 — there are helper macros designed to make setting up this struct properly way easier and to cut down on those common silly mistakes. Go look at the jwt_set_{SET,GET}_{INT,STR,BOOL,JSON} definitions. Trust. 🫶

---

🔥 Field Documentation 🔥

🧚 union { ... } jwt_value_t

The anonymous union hanging out inside jwt_value_t — this is where the actual value lives, in whichever flavor you picked. 🌈

💜 int jwt_value_t::bool_val

The boolean value slot, fr fr.

🍓 jwt_value_error_t jwt_value_t::error

Where the error lands. Check her, always. 😭

🌸 jwt_long_t jwt_value_t::int_val

The integer value slot, periodt.

🦋 char* jwt_value_t::json_val

The JSON value slot, no cap.

✨ const char* jwt_value_t::name

The name — like, the name of the header or claim you're dealing with. 👑

🎀 int jwt_value_t::pretty

The pretty flag. Do with that what the docs say, bestie 💅

💖 int jwt_value_t::replace

The replace flag. Also exactly what it says on the tin 🔥

⭐ const char* jwt_value_t::str_val

The string value slot. Iconic.

🌈 jwt_value_type_t jwt_value_t::type

The type of this value — she decides which union member is the main character 🌟

---

👑 Author 👑

Generated automatically by Doxygen for LibJWT from the source code. (Yeah, a robot wrote it. Still ate. 💀)

---

And that's the whole vibe check, bestie 🫶 this page is from LibJWT, Version 3.3.3, and it's the jwt_value_t(3) girlie herself — go slay some JWTs, mwah 💖✨