Should we add selectManyFromResult to the core or leave it to the consumer to implement it

[dzena]

export function selectManyFromResult<T extends QueryObserverResult, R>(
	ids: any[]
): OperatorFunction<T, R[] | undefined> {
	return pipe(
		filter(({ data }) => Array.isArray(data)),
		selectResult(({ data }) => {
			if (Array.isArray(data)) {
				return data?.filter(({ id }) => ids.includes(id));
			}
			throw new Error("Data not an array");
		}),
		distinctUntilArrayItemChanged()
	);
}


// c/p from Elf
export function distinctUntilArrayItemChanged<T>(): MonoTypeOperatorFunction<T[] | undefined> {
	return distinctUntilChanged((prevCollection: T[] | undefined, currentCollection: T[] | undefined) => {
		if (prevCollection === currentCollection) {
			return true;
		}

		if (prevCollection?.length !== currentCollection?.length) {
			return false;
		}

		const isOneOfItemReferenceChanged = currentCollection?.some((item, i) => {
			return prevCollection?.[i] !== item;
		});

		// return false means there is a change and we want to call next()
		return !isOneOfItemReferenceChanged;
	});
}

He there @NetanelBasal. We are contemplating on using the ng-query in our project and we started looking into the source code. I believe this operator could be useful.
If you agree, I can submit a PR. In that case, would you export selectManyFromResult from operators or rather entity-utils?
I'll try to find some time in the coming days to take care of implementing the playground with "Table Filtering and Sorting".

Really appreciate the work you guys are doing. Keep on rocking!

Edit. Please neglect TS for now. I'll take care of that later.

[NetanelBasal]

I don't think it should be in the library for now. Let's see how many people need it. You can add it to your project for now.