swagger-api/swagger-codegen

Review serialization and deserialization of `date` property

Open

#5,531 opened on May 2, 2017

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

Repository metrics

Stars
 (12,701 stars)
PR merge metrics
 (No merged PRs in 30d)

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

Research direction
Review the serialization/deserialization logic for the date property in the codebase, focusing on the handling of RFC3339 full date format. Trace through the template driven code generation to identify the relevant templates and generators. Write test cases in the Petstore sample client to cover the date serialization/deserialization.
Tech stack
None
Domain
api
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.
Clear
Prerequisites
GitOpenAPI
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60