This should have been done in 19865e5f probably, before the latest
release. This generally causes users of the library to cargo update
manually.
Signed-off-by: pep <pep@bouah.net>
serde was bypassing the validation these types rely on, making them
completely unsound in an XMPP context.
Fixes #165.
Link Mauve
created
f1e5ac6
xmpp-parsers: Make Priority’s inner i8 pub
Click to expand commit body
We forgot to make it pub before, but should have.
This was a regression from 893a2f8e47e8aabdec0797994f160423860b68db,
when we converted it to xso.
Fixes #166.
Link Mauve
created
8c2b1df
xmpp-parsers: Fix the type of jingle_rtp/ssrc to u32
Click to expand commit body
XEP-0167 has been updated to version 1.2.3, to change the type of the
'ssrc' attribute to u32 (from String). This is in accordance with
RFC 3550 (RTP), which defines it as a randomly-chosen 32-bit unsigned
integer.
Additionally, the docstring was completely wrong.
Link Mauve
created
e22daa9
xmpp: make Agent.config accessible only via getter
Click to expand commit body
It may not matter much for the moment as this struct shouldn't change
very much during the life of the client, but this prevents the lock from
being held too long.
Signed-off-by: pep <pep@bouah.net>
pep
created
a1a31ce
xmpp: Merge Agent configuration into new Config struct
Click to expand commit body
Signed-off-by: pep <pep@bouah.net>
pep
created
147b79c
xmpp: new Config struct for Agent, with bookmarks_autojoin for now
Click to expand commit body
Signed-off-by: pep <pep@bouah.net>
pep
created
77acd92
tokio-xmpp: Ignore missing "version" stream attribute for 0114 components
Click to expand commit body
From the prosody@ room:
- 0114 doesn't mention the removal of @version on the stream, and it
refers to 3920 which has it as a MUST.
- 0114 streams have historically never used @version="1.0"
- @version="1.0" implies stream features which 0114 doesn't have.
- There was a proposal years ago to fix this but a new XEP was preferred
(0225).
The change here uses a compile-time check, and may have to change when
support for 0225 arrives if it's still gated behind the "component"
feature (even though it may be weird to have both under the same
feature). We'll see when we get there.
Signed-off-by: pep <pep@bouah.net>
This doesn't fix all of the clippy warnings in these crates. There are
decisions that needs to be made in there that I'm not willing to make.
Signed-off-by: pep <pep@bouah.net>
d60f718
xmpp/example: Use unwrap instead of ignoring Result
Click to expand commit body
skip-changelog.
Co-authored-by: Link Mauve <linkmauve@linkmauve.fr>
Signed-off-by: pep <pep@bouah.net>
pep
and
Link Mauve
created
21cb5c1
xmpp/example: explicit types to prevent mishap
Click to expand commit body
Previously there was a forgotten `.await` at this exact place because of
the `let _`, which could have been `let _: type` to prevent this. The
`handle_events` method here returns the unit type so I just removed it.
skip-changelog: already in the changelog and not released yet
Signed-off-by: pep <pep@bouah.net>
As it's now being used in Element::attr and ElementBuilder::attr
Signed-off-by: pep <pep@bouah.net>
pep
created
19865e5
minidom: breaking: Allow getting Element attributes by namespace
Click to expand commit body
- Move Element.attributes to `AttrMap`, slowly using rxml's features and
unrolling our own.
- Add Element::attr_ns that requires the attribute namespace.
Element:attr defaults to rxml::Namespace::none() but the interface
changes nonetheless for a &NcNameStr. Similar changes on
`ElementBuilder` methods.
- Remove iterator structs for attributes, return a ref on the AttrMap
directly as we don't need to keep attributes' internals hidden
anymore.
- Enable rxml's `macros` feature within tests to access the `xml_ncname`
macro.
Signed-off-by: pep <pep@bouah.net>