x-miro is added in the resolved spec even after explicitly setting preserveMiro: false

[Shwetap05]

Using latest npm package of speccy and even after setting preserveMiro: false in options, seeing it added in resolved spec, when loading this spec in swagger editor its complaining about it.

[pderaaij]

In what file do you set the options?

[Shwetap05]

Calling speccy from typescript code like below and passing the option there.

private static options = {
        resolve: true,   // Resolve external references
        jsonSchema: true, // Treat $ref like JSON Schema and convert to OpenAPI Schema Objects
        preserveMiro: false // Flag to resolver as to whether to preserve old value of $ref in x-miro
      };

    static async ResolveReferences(documentUrl: string)
    {
        return new Promise<string>(async (resolve,reject) => {
            loader.loadSpec(documentUrl,SpeccyClient.options,(err,data ) => {
                if (err) {reject(err);}
                else {resolve(JSON.stringify(data));}
            })
        })
    }

[NathanAtKadaster]

I'm having this issue using the docker image as well. I don't think the x-miro extensions should be in a resolved spec at all. Default behaviour should be preserveMiro: false. I thought this was fixed as per #187 and #198, but it looks like this behaviour is still there in 0.9.0.

I was using Docker image wework/speccy:0.9.0 and still get invalid specs after resolving.

[dlouzan]

I'm also experiencing this, plus the generated code goes against one of the lint rules:
https://speccy.io/rules/1-rulesets#reference-no-other-properties

[MikeRalphson]

Anyone with a nice short input definition as a repro case?

[dlouzan]

I have just added a new issue in oas-kit for this

[timonbimon]

also having the same issue :(

[djtarazona]

Fixed here Mermade/oas-kit#152 (comment)