Use Symbol.for to create Symbol.observable if it does not exist.

[jamestalmage]

This is the method used by symbol-observable and other packages (including RxJs/Observables).

The current usage is causing false negatives from the is-observable package in latest Node.

[sindresorhus]

Maybe zen-observable could just use https://github.com/blesh/symbol-observable? // @Blesh

[zenparsing]

That would probably be better.

[jamestalmage]

Oh dear. symbol-observable just changed their way of doing it. It now explicitly does NOT use Symbol.for: benlesh/symbol-observable#7

I considered recommending symbol-observable - but you were dependency free, so thought that might be a priority.

[zenparsing]

I like dependency-free : )

I'll comment over on symbol-observable.

[sindresorhus]

You could always just copy-paste it. I'm more concerned about consistent behavior.

[benlesh]

@zenparsing you might want to roll this one back, as it doesn't match prior art like Symbol.iterator.

Symbol.iterator === Symbol.for('iterator'); // false

[benlesh]

... or just use symbol-observable, as @sindresorhus suggested. lol

[jamestalmage]

You could always just copy-paste

I basically did. It just changed a day later

[jamestalmage]

you might want to roll this one back, as it doesn't match prior art like Symbol.iterator.

Yeah, but which one is right? Who decides this stuff? It seems really important to get it right, better to do it now. Who pushed the Symbol spec through? Let's ask them.

[benlesh]

Yeah, but which one is right?

WRT Symbol.iterator The existing one is "right", for better or worse. It's in the wild and is not going to change.

Who decides this stuff?

The TC39, after exhaustive discussion and debate, I suppose.

Who pushed the Symbol spec through? Let's ask them.

People like @zenparsing and friends.