inspect reserved keyword for class function

[aabfred]

• Version: v7.3.0 (npm v3.10.10)
• Platform: GNU/Linux Fedora release 25 (Twenty Five) 4.8.15-300.fc25.x86_64

class MyClass {
    constructor(){ ... }
    inspect(){
        ... some code for a function I create ...
    }
}
Promise.all([new MyClass()]).then(console.log)

=> [ Promise { < pending > } ] !!!

I've found the reason here: Custom inspection functions on Objects
What a bad idea !!! It's a real bug factory

To add such features without being intrusive, your syntax should look like:

class MyClass {
    constructor(){ ... }
    [Symbol.for("inspect")](depth, options){ ... }
}

[addaleax]

You’re totally right! See #8071 for some previous discussion on that. In short, we do support Symbol-based inspection now, and it can even be used to override the “inspect” name.

Unfortunately, getting rid of “inspect” as the name for the method is not too easy due to the required backwards compatibility – “inspect” is a lot older than Symbols in Javascript, so back then the choice made sense, and by now a lot of people have come to rely on that behaviour.

If you have any suggestions for improving the situation that are not breaking changes, that would be hugely appreciated.

[aabfred]

You're right, sorry.
If you can, remove this item or tell me a way to do it.

[addaleax]

If you can, remove this item or tell me a way to do it.

This item? I’m not sure what you mean.

In any case, adding a [util.inspect.custom]() { return this; } method to your class should solve your particular problem.

[jasnell]

Assuming this can be closed now