History

ruma-events: Create separate to-device content structs

While it's possible to share the content between different event types
in the usual case some event types have slightly different contents if
they are sent out as a to-device event vs a room message event.

The canonical example for this are key verification events where the
to-device version has a transaction id field but the room message
version uses event relationships for the same purpose.

This patch makes it possible for to-device events to have different
content structs. Type aliases are used where a common struct can be
used.

2020-12-04 19:48:34 +01:00

src

ruma-events: Create separate to-device content structs

2020-12-04 19:48:34 +01:00

Cargo.toml

Update authors field in ruma-events-macros/Cargo.toml

2020-09-22 21:04:00 +02:00

CHANGELOG.md

Update changelog for ruma-events-macros

2020-07-29 16:54:11 +02:00

README.md

Update links to main branch

2020-10-13 10:24:54 +02:00

README.md

ruma-events-macros

ruma-events-macros provides a procedural macro for easily generating event types for ruma-events.