view .jshintrc @ 39121:7c6044634957

help: describe more detail about capabilities while deciding merge tool

"hg help merge-tools" describes as below:

    (internal merge tools) will by default not handle symlinks or
    binary files.

But in some cases, Mercurial assumes that internal merge tools have
one or both of these capabilities.

"hg help merge-tools" also describes as below, for matching patterns in
merge-patterns configuration section. But this is not sufficient.

    Here, binary capabilities of the merge tool are not considered.

This patch describes more detail about capabilities while deciding
merge tool.

{
    // 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)
}