-
Type:
Epic
-
Resolution: Unresolved
-
Priority:
Minor - P4
-
None
-
Affects Version/s: None
-
Component/s: None
-
ConnectionString WHATWG URL Spec Alignment
-
Not Needed
-
To Do
-
None
-
0
-
0
-
0
-
100
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Summary
Today, our connection strings spec is inspired by (and parsing aims to align with) RFC3986. Connection string parsing should more-closely follow WHATWG URL's spec (https://url.spec.whatwg.org/) which aims to succeed RFC3986 and is the industry standard.
Motivation
Who is the affected end user?
Users of our drivers, maintainers.
Who are the stakeholders?
How does this affect the end user?
The end user may end up with connection issues due to spec compliance issues as we attempt to develop our parser against a leading indicator (WHATWG URL is the standard, but we attempt to align to RFC3986). Users may also treat the connection string as a URL, expecting WHATWG URL compliance, which is non-ideal.
How likely is it that this problem or use case will occur?
An case bug has already been identified (e.g: https://github.com/mongodb-js/mongodb-connection-string-url/pull/125#discussion_r3469585729) where existing parsing failures against a url (which should be valid to the underlying RFC).
If the problem does occur, what are the consequences and how severe are they?
Minor annoyances. One known customer reported bug, with low severity (workarounds exist)
Is this issue urgent?
Non-urgent
Is this ticket required by a downstream team?
No
Is this ticket only for tests?
No
Cast of Characters
Engineering Lead:
Document Author:
POCers:
Product Owner:
Program Manager:
Stakeholders: