Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

V1 #88

Closed
wants to merge 0 commits into from
Closed

V1 #88

wants to merge 0 commits into from

Conversation

rlebran
Copy link
Contributor

@rlebran rlebran commented Jun 2, 2024 •
edited
Loading

Use schemars v1.
Switching to schemars v1 should offer us the possibility to add OAS3.1 support.

Todo:

  • Take schema generator or settings as an argument for ApiComponent::schema and ApiComponent::child_schemas
  • Remove unwrap/expect when using Schema::try_from
  • Remove json_schema!
  • Update schemars / use fork to fix multiple enum flatten
  • Update examples

@rlebran rlebran added the enhancement New feature or request label Jun 2, 2024
@rlebran rlebran marked this pull request as draft June 2, 2024 08:42
@rlebran rlebran force-pushed the schemars-v1 branch 2 times, most recently from 388be26 to 2ded2e0 Compare June 23, 2024 11:09
@rlebran rlebran changed the title Chore: use schemars v1 V1 Jun 27, 2024
@rlebran rlebran linked an issue Jun 27, 2024 that may be closed by this pull request
Assess how to support OAS 3.1 #39
Open
@rlebran rlebran force-pushed the schemars-v1 branch 4 times, most recently from 8079e74 to e4dceb2 Compare July 11, 2024 08:55
@rlebran rlebran closed this Jul 11, 2024
@rlebran rlebran deleted the schemars-v1 branch July 11, 2024 09:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Assess how to support OAS 3.1
1 participant
@rlebran