Clarification on value delimiter for key expression parameters

[gar1t]

Describe the bug

There appears to be a discrepancy between the docs and the implementation regarding the separation char for param name/value pairs used in key expressions.

The docs specify &.

From the source code docs:

When in string form, selectors look a lot like a URI, with similar semantics:
...
parameters are separated by &

This is consistent with the referenced description in the roadmap repo.

However, the implementation uses ;.

I can confirm that params specified as foo?bar=123&baz=456 results in a single param bar of 123&baz=456.

foo?bar=123;baz=456 yields the two params foo and bar.

I didn't see any user facing examples that call attention to this issue one way or another.

To reproduce

See description.

System info

Applies to any system.