Would there be any conflict between the default fetch behaviour Next supports and the fetch functions created in OpenApiGen's Typescript-Fetch generator?
I assume not but the only other querying service I have worked with is RTKQ, which does have its own memoized fetch router and conflict, so thought I'd try find out.