swagger-api/swagger-codegen

Review serialization and deserialization of `date` property

Open

#5531 opened on May 2, 2017

View on GitHub
 (0 comments) (0 reactions) (0 assignees)HTML (12,701 stars) (5,474 forks)batch import
Enhancement: CI/Testhelp wanted

Description

Description

Review serialization and deserialization of date property as it might not be (de)serialized correctly to full-date in RFC3339

Swagger-codegen version

Latest master

Related issues

https://github.com/swagger-api/swagger-codegen/issues/5513

Suggest a Fix

We'll need to write test cases in Petstore sample client to cover this.

Contributor guide

Tech stack
javarest api
Domain
testingapi
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
OpenAPI specificationRFC3339 date formatJava testing
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Investigate how the swagger codegen currently handles the 'date' property serialization, comparing with RFC3339 full date format. Refer to related issue #5513. Write test cases in the Petstore sample client (e.g., swagger codegen/samples/client/petstore/java) to verify correct (de)serialization.