macros: Use a nicer syntax when declaring attributes.
The previous version had a => required|optional|default token, this was duplicating information for Option types and didn’t look very good. This new version looks like a type, which can be either Required<_>, Option<_> or Default<_>, and means the same thing.
This commit is contained in:
parent
f2c3f45a6f
commit
bcd42a26e3
27 changed files with 162 additions and 137 deletions
|
|
@ -169,16 +169,16 @@ generate_element!(
|
|||
Content, "content", JINGLE,
|
||||
attributes: [
|
||||
/// Who created this content.
|
||||
creator: Creator = "creator" => required,
|
||||
creator: Required<Creator> = "creator",
|
||||
|
||||
/// How the content definition is to be interpreted by the recipient.
|
||||
disposition: Disposition = "disposition" => default,
|
||||
disposition: Default<Disposition> = "disposition",
|
||||
|
||||
/// A per-session unique identifier for this content.
|
||||
name: ContentId = "name" => required,
|
||||
name: Required<ContentId> = "name",
|
||||
|
||||
/// Who can send data for this content.
|
||||
senders: Senders = "senders" => default
|
||||
senders: Default<Senders> = "senders",
|
||||
],
|
||||
children: [
|
||||
/// What to send.
|
||||
|
|
|
|||
Loading…
Reference in a new issue