OperationID from embedded spec doesn't match the original spec #1274
Description
Version: v1.15
I'm not sure if this is by design, but given an OAPI spec
openapi: "3.0.0"
info:
title: "my spec"
version: 1.0.0
paths:
/pet:
get:
operationId: getPet
responses:
200:
content:
application/json:
schema:
type: stringOperationId from the embedded spec is set as GetPet rather than getPet. I used the generated GetSwagger() function to convert embedded spec to openapi3.T object.