v0.2.9

Relativize: avoid panic in case of shared UTF-8 prefix

v0.2.8

Fixes relativize on IRIs with a scheme and nothing else.

v0.2.7

Fixes relative IRI resolution when there is no authority but a path starting with "/".

v0.2.6

Fixes relativize on hierarchical paths without authority and starting slash.

v0.2.5

Adds Iri::relativize to build a relative IRI from a base IRI and an absolute IRI.

v0.2.4

ipvFuture are now allowed and some characters are now disallowed in some places to follow RFC 3987.

v0.2.3

Adds _unchecked methods for faster parsing/resolving if the IRI is known to be valid.

v0.2.2

Iri and IriRef now implement Serde Serialize and Deserialize traits if the serde crate is present. The serialization is a plain string.

v0.2.1

Changed

• Fixes a regression in relative IRI parsing when there is only a host without a training slash. For example foo is now resolved against http://example.org as http://example.org/foo and not anymore as http://example.orgfoo.
• The validation of unicode character is now carefully following RFC 3987:
  • Some private use characters are not anymore allowed in path and fragment.
  • Some surrogates are not allowed anymore in query.
  • The range F900-FDEF is now allowed in path and fragment following the RFC.

v0.2.0

Added

• IriRef type that provides the same API as Iri but for relative IRIs.
• PartialOrder implementations between Iris with different container types.

Changed

• Fixes path resolution: the resolver should return tag:c-d and not tag:/c-d when resolving c-d against tag:a-b.
• Relative IRIs are not anymore allowed to start with a column :.
• iprivate characters (%xE000-F8FF / %xF0000-FFFFD / %x100000-10FFFD) are not allowed anymore as part of the IRI query component following RFC 3987.