why connect() does not return a promise ?

[davibe]

Since most of the api is promised, i was wondering why connect() function is not.

It looks bad (example: https://gist.github.com/davibe/8986a865a96005fa2467)

[vkarpov15]

You're right, worth adding this.

[davibe]

probably the same goes for disconnect()

[Jokero]

+1

[xpepermint]

+1

[bsonntag]

+1

[Jokero]

@vkarpov15 How to handle mongoose.connect() error in catch handler? I want to use application initialization chain but can't do that because mongoose.connect() does not return rejected promise.
It returns rejected promise only if I specify callback, but it's not a perfect solution.

Example:

mongoose.connect('mongodb://127.0.0.2/test')
    .then(() => {
        return server.start();
    })
    .catch(err => { // <---- we will not be here...
        console.error('App starting error:', err.stack);
        process.exit(1);
    });

Workaround:

mongoose.connect('mongodb://127.0.0.2/test', function() { /* dummy function */ })
    .then(() => {
        return server.start();
    })
    .catch(err => { // mongoose connection error will be handled here
        console.error('App starting error:', err.stack);
        process.exit(1);
    });

[vkarpov15]

@Jokero that's odd. Can you open up a separate issue for this?