[BUG][RUBY-NEXTGEN] format: date properties stay String after from_hash

Abierto
#25,721 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@Inf1mum ya está trabajando en esto.

Desde el 19/11/2026.

  • #25760 de @Inf1mum — abierto

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
62/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
ruby
Área
backend

Línea de trabajo

Start in the Ruby nextgen model code at Polymorphism.coerce and Polymorphism.cast_raw, where the issue says Time handling exists but Date handling is missing. Trace how from_hash converts a format: date property and how anyOf/oneOf candidates are matched. Add coverage for both cases; done when the property becomes a Date and the date candidate matches.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Bug Report Checklist
  • Have you provided a full/minimal spec to reproduce the issue?
  • Have you validated the input using an OpenAPI validator?
  • Have you tested with the latest master to confirm the issue still exists?
  • Have you searched for related issues/PRs?
  • What's the actual output vs expected output?
Description

A format: date property is declared with type: 'Date', but neither Polymorphism.coerce nor Polymorphism.cast_raw has a Date branch (Time has one). The value is left as a String by from_hash, and a Date candidate of an anyOf/oneOf never matches.

openapi-generator version

master, 7.28.0-SNAPSHOT, 8a9fb722777e770e2c44b20b00bddbb51a0d525a

OpenAPI declaration file content or url
openapi: 3.0.3
info:
  title: probes
  version: 1.0.0
paths:
  /greeting:
    get:
      operationId: getGreeting
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                type: string
  /pets:
    get:
      operationId: listPets
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                type: array
                items:
                  $ref: '#/components/schemas/Pet'
components:
  schemas:
    Pet:
      type: object
      properties:
        birthday:
          type: string
          format: date
        code:
          type: string
          pattern: '^[a-z]+$'
Generation Details
java -jar openapi-generator-cli.jar generate -g ruby-nextgen -i spec.yaml -o out \
  --additional-properties=gemName=petstore,moduleName=Petstore
Steps to reproduce
$LOAD_PATH.unshift 'out/lib'
require 'petstore'

pet = Petstore::Models::Pet.from_hash('birthday' => '2026-01-02')
p pet.birthday
p pet.birthday.class

Actual (ruby 4.0.9, faraday 2.15.1):

"2026-01-02"
String

Expected:

#<Date: 2026-01-02 ((2461043j,0s,0n),+0s,2299161j)>
Date
Related issues/PRs

Raised by the automated review of #25717; the code is already on master and is not changed by that PR.

Lenguaje dominante
Java
Estrellas
26.9k
Forks
7.8k
Merge medio
2 d 23 min
PR fusionados (30 d)
177

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de OpenAPITools/openapi-generator

Todos los issues de OpenAPITools/openapi-generator

Issues similares

Más issues de Java

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.