fix(resolvers): fix generating schema for alias object

[bluebeel]

Status

READY

Description

resolveRef expect as input one of the following options:

{ '$ref': '#/components/schemas/Error' }

{ type: 'array', items: { '$ref': '#/components/schemas/Pet' } }

{
  type: 'object',
  required: [ 'id', 'name' ],
  properties: {
    '@id': { type: 'string', format: 'iri-reference' },
    id: { type: 'integer', format: 'int64' },
    name: { type: 'string' },
    tag: { type: 'string' },
    email: { type: 'string', format: 'email' },
    callingCode: { type: 'string', enum: [Array] },
    country: { type: 'string', enum: [Array] }
  }
}

But it's possible for a schema to reference another schema (alias)

{
  name: 'fileType',
  in: 'path',
  description: 'the file type of verifications Identity.',
  required: true,
  schema: { '$ref': '#/components/schemas/EIdentityFileType' }
}

in that case the resolver will crash since he doesn't manage to find the $ref.

[vercel]

Someone is attempting to deploy a commit to a Personal Account owned by @anymaniax on Vercel.

@anymaniax first needs to authorize it.

[anymaniax]

Thanks 🎉