summaryrefslogtreecommitdiff
path: root/.sqlx/query-46c94988ed02829744cff50bcbfa9b4638273c89ceafd0790c7c372e6954619a.json
diff options
context:
space:
mode:
authorOwen Jacobson <owen@grimoire.ca>2025-10-24 19:03:02 -0400
committerOwen Jacobson <owen@grimoire.ca>2025-11-05 17:22:18 -0500
commite2a851f68aacd74a248e925ab334c3cf9eabba18 (patch)
tree5cc735543fbf75b1d6810e2ca8c0bc197269de3c /.sqlx/query-46c94988ed02829744cff50bcbfa9b4638273c89ceafd0790c7c372e6954619a.json
parente08c3fa46aa48ac5cbeb75f52fc27d4061e2fa62 (diff)
Move the VAPID public key encoding into a serde-compatible encoding module.
The [Serde attribute docs][serde-attr] don't spell out that this will work, but experimentally, it looks like a module used with `#[serde(with)]` only needs to have the `encode`/`decode` functions if they're actually used, and can be "incomplete" if the missing ones are also unused in your code. That's the case here: we serialize VAPID keys, but never deserialize them. [serde-attr]: https://serde.rs/field-attrs.html#with This improves organization a bit in my view, but more importantly it also sets us up for a coming change where we _will_ start deserializing VAPID keys, and where I'd like to use the same logic: giving it its own module will make that easier to organize.
Diffstat (limited to '.sqlx/query-46c94988ed02829744cff50bcbfa9b4638273c89ceafd0790c7c372e6954619a.json')
0 files changed, 0 insertions, 0 deletions