swagger-api / swagger-api/swagger-codegen

Review serialization and deserialization of `date` property

Open
#5,531 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Enhancement: CI/Test help wanted
Dominant language
Mustache
Stars
17.8k
Forks
6k
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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Read related issue #5513 first, then inspect the Petstore sample client and its existing serialization tests. Add test coverage for serialization and deserialization of the date property, with completion measured by correct RFC3339 full-date handling.

Written by the indexing model from the issue text.

Assessment

Domain
api, testing
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.