We are trying to import the OpenAPI document generated by APIDog and found the tag “faker” in the paths properties and components. “faker” is not part of the OpenAPI spec and should be prefaced with x- to denote a custom field as x-faker. It’s breaking our import into Microsoft’s APIM platform and is adding a manual step to the process, making Apidog’s document no longer the “source of truth.”
Thanks for the feedback, I think this is indeed a mistake, and we will fix it.