view .jshintrc @ 40663:c53f0ead5781

http: allow 'auth.prefix' to have a username consistent with the URI

It may be a little weird to put a username in the prefix, but the documentation
doesn't disallow it, and silently disallowing it has caused confusion[1].  The
username must match what is passed in (which seems to be from the URI via a
circuitous route), as well as 'auth.username' if it was specified.  I thought
about printing a warning for a mismatch, but we already don't print a warning if
the 'auth.username' and URI username don't match.

This change allows the first and second last new test cases to work as expected.
It looks like this would have been a problem since at least 0593e8f81c71.

[1] https://www.mercurial-scm.org/pipermail/mercurial/2018-November/051069.html

{
    // Enforcing
    "eqeqeq"        : true,     // true: Require triple equals (===) for comparison
    "forin"         : true,     // true: Require filtering for..in loops with obj.hasOwnProperty()
    "freeze"        : true,     // true: prohibits overwriting prototypes of native objects such as Array, Date etc.
    "nonbsp"        : true,     // true: Prohibit "non-breaking whitespace" characters.
    "undef"         : true,     // true: Require all non-global variables to be declared (prevents global leaks)

    // Environments
    "browser"       : true      // Web Browser (window, document, etc)
}