Created by: yjh0502
PR checklist
-
Read the contribution guidelines. -
Pull Request title clearly describes the work in the pull request and Pull Request description provides details about how to validate the work. Missing information here may result in delayed response from the community. -
Run the following to build the project and update samples: ./mvnw clean package ./bin/generate-samples.sh ./bin/utils/export_docs_generators.sh
./bin/generate-samples.sh bin/configs/java*
. For Windows users, please run the script in Git BASH. -
File the PR against the correct branch: master
,5.3.x
,6.0.x
-
If your PR is targeting a particular programming language, @mention the technical committee members, so they are more likely to review the pull request.
description
It adds support for integer-typed enums to rust client binding. Here's example schema:
openapi: 3.0.1
info:
title: test
version: v1
servers:
- url: http://127.0.0.1:3000/
paths:
/testapi:
post:
responses:
'200':
$ref: '#/components/schemas/Test'
components:
schemas:
Test:
type: integer
enum:
- 101
- 102
output for the schema is as follows:
#[repr(i64)]
#[derive(Clone, Copy, Debug, Eq, PartialEq, Ord, PartialOrd, Hash, Serialize_repr, Deserialize_repr)]
pub enum Test {
_101 = 101,
_102 = 102,
}
impl ToString for Test {
fn to_string(&self) -> String {
match self {
Self::_101 => String::from("101"),
Self::_102 => String::from("102"),
}
}
}
Current implementation assumes all enums are string-represented so the schema above fails to decode int-encoded enums. This PR adds support for int-typed enums with [repr(i64)]
.
cc @paladinzh