BUG: RTK Query: You can no longer set 'maxRetries' to 0

[ritterb82]

In the latest update there was updates to the retry logic. But the updates broke the ability to set maxRetries to 0. I believe this is due to the possibleMaxRetries array that now exists and gets filtered by Boolean. Which cause 0 to be tossed out.

So then at that point, it just goes back to the default of 5.

redux-toolkit/packages/toolkit/src/query/retry.ts

Lines 82 to 87 in f7a8282

	const possibleMaxRetries: number[] = [
	5,
	((defaultOptions as any) || EMPTY_OPTIONS).maxRetries,
	((extraOptions as any) || EMPTY_OPTIONS).maxRetries,
	].filter(Boolean)
	const [maxRetries] = possibleMaxRetries.slice(-1)

[OliverRadini]

Would it be alright if I picked this up? Looking to find some issues to work on and this seems interesting

[markerikson]

Sure, please do!

[OliverRadini]

@markerikson thanks, hopefully the code in the PR properly resolves the issue

[markerikson]

Out in https://github.com/reduxjs/redux-toolkit/releases/tag/v1.9.1