Linting Problem with Constructor about gun HOT 5 CLOSED

GUN figures out whether you need to use new for you:

    function Gun(opt){
        var gun = this;
        if(!Gun.is(gun)){
            return new Gun(opt);
        }
        gun.opt(opt);
    }

So that way you don't have to worry about it. I think you can call it explicitly and it'll still work just fine var gun = new Gun(...); but I should probably write tests to guarantee that. This just protects against common forgetfulness and it doesn't have any side effects.

from gun.

Okay, cool. It's more that I want to make sure that using new still works, since my linter is throwing a warning whenever it comes across not using it.

from gun.

I suggest also exposing a '.create()' method, as that's the conventional way to expose the constructor when you want to avoid new.

from gun.

Documented. @PsychoLlama may make an extension which adds a .create() method.

from gun.

Gun.create() has been added as a code snippet, found here

from gun.