From bfc36cd12e4e266ebf8870a38333499c3d4c2b71 Mon Sep 17 00:00:00 2001 From: "ben.durrant" Date: Tue, 28 Mar 2023 11:12:49 +0100 Subject: [PATCH] update tip regarding overrideExisting to match actual behaviour --- docs/rtk-query/usage/code-splitting.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/rtk-query/usage/code-splitting.mdx b/docs/rtk-query/usage/code-splitting.mdx index 436600d6f3..af757eaa96 100644 --- a/docs/rtk-query/usage/code-splitting.mdx +++ b/docs/rtk-query/usage/code-splitting.mdx @@ -56,5 +56,5 @@ export const { useExampleQuery } = extendedApi ``` :::tip -In development mode, if you inject an endpoint that already exists and don't explicitly specify `overrideExisting: true`, the endpoint will not be overridden and you will get a warning about it. You **will not see the warning in production** and the existing endpoint will just be overriden, so make sure to account for this in your tests. +If you inject an endpoint that already exists and don't explicitly specify `overrideExisting: true`, the endpoint will not be overridden. In development mode, you will get a warning about this. :::