When loading the override files from this folder, the spec_definitions_service.ts relies on the filenames to match the generated definitions with the overrides (see here). Then both definitions are merged, but if the name of the endpoint differs in the content of the file, that can introduce wrong definitions mapping. The service code should check that the name of the endpoint in the file is the same as the file name. Possibly throw an error or warning if that happens to alert the dev team about this issue.
See this PR that introduces the error in the override files and this commit that manually fixes that.
When loading the override files from this folder, the
spec_definitions_service.ts
relies on the filenames to match the generated definitions with the overrides (see here). Then both definitions are merged, but if the name of the endpoint differs in the content of the file, that can introduce wrong definitions mapping. The service code should check that the name of the endpoint in the file is the same as the file name. Possibly throw an error or warning if that happens to alert the dev team about this issue. See this PR that introduces the error in the override files and this commit that manually fixes that.