LIGHTNING-NOTIFI...EPRECATED_ONESHOT(7)

πŸ“¦
version 26.06.9 Β· 2 versions
, in nixpkgs unstable

πŸ’… NAME πŸ’…

ok so bestie, let me introduce you to deprecated_oneshot β€” literally the Notification for per-command deprecation settings ✨. She's a section 7 girlie, and her full government name on the header is LIGHTNING-NOTIFI...EPRECATED_ONESHOT(7) (yes, truncated with the dots and everything, that's not me being lazy, that's just how the page title rolls 😭).


πŸ¦‹ DESCRIPTION πŸ¦‹

So this notification was added in v24.02 β€” not brand new but still new enough to be cute about it. πŸ’–

Here's the tea: the deprecated_oneshot notification informs a plugin that the immediately following command uses different deprecation handling than the global setting. Like, the global setting is the main character, but for exactly one command the rules are giving something else, and this notification is the heads-up text in the group chat so your plugin isn't left on read. πŸ”₯

No cap, that's the whole vibe check.


πŸŽ€ NOTIFICATION PAYLOAD πŸŽ€

  • deprecated_ok (boolean) β€” Whether deprecated APIs are allowed for the immediately following command. That's the entire payload, she's a one-field icon and we respect it. πŸ‘‘

lowkey a tiny page but every bit of her matters, okay? deprecated_ok is a boolean, not a maybe, not a "we'll see" β€” a straight boolean. 🫢

and that's the whole page, bestie β€” brought to you by Core Lightning v26.06.9, slaying in section 7, mwah πŸ’œπŸŒ·βœ¨

πŸ“¦ where this page comes from