lambdaisland.uri.normalize/normalize-query
which did
not take into account utf-16 encoding.lambdaisland.uri.normalize/normalize
now also normalizes the fragment.uri-str
as an explicit lambdaisland.uri.URI
to string conversionURI
back to a string needs to be
done explicitly with uri-str
, and it is not possible to use a URI as a
function. ((:path uri)
is ok, (uri :path)
is not).uri?
predicate.+
as space, so the conversion between maps and
query strings correctly round trips.lambdaisland.uri.platform/string->byte-seq
return unsigned bytes on
both plaforms (clj/cljs)assoc-query
/ query-encode
encode spaces as "+" rather than "%20",
which brings it in line to how most languages/libraries do it.query-string->map
,
map->query-string
, query-map
, query-encode
, assoc-query
,
assoc-query*
.=
and +
there is a semantic difference between the encoded and decoded form, when they
are encoded in the input normalization should not decode them and vice versalambdaisland.uri.normalize/normalize
, for normalizing URI instances.absolute?
and relative?
uri
, join
, coerce
, parse
, edn-readers
Can you improve this documentation? These fine people already did:
Arne Brasseur, FiV0 & Andrey AntukhEdit on GitHub
cljdoc is a website building & hosting documentation for Clojure/Script libraries
× close