Selector being called when nothing changed

I’m using

aurelia-framework: 1.3.1
aurelia-store: 1.4.0

Using this basic code:

	selector: {
		someData: (store) => store.state.pipe(pluck("someData"))

// inside component
private someDataChanged(newValue: SomeData, oldValue: SomeData) {

I can inspect the payload newValue & oldValue. Sometimes these values are not even the SomeData type.

It’s like the selector is subscribing to the entire state and every state change. The work around that has been used is guard statements to inspect the contents of newValue

Surely this isn’t intended behaviour for a selector?

Looks like your question was answered before.