Skip to content

v3.2: Define a policy for deprecation markings. #4591

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.

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

Merged
merged 2 commits into from
May 19, 2025

Conversation

handrews
Copy link
Member

We already deprecate example in the Schema Object, but do not define what deprecations means. We also effectively deprecate allowEmptyValue in the Parameter Object but did not explicitly say so. We will likely make other deprecations in the future.

This defines a very basic deprecaton policy (they are still supported, but we reserve the right to define a policy for removing them in the future) and marks allowEmptyValue with the same formatting used for example.

  • schema changes are included in this pull request
  • schema changes are needed for this pull request but not done yet
  • no schema changes are needed for this pull request

We already deprecate `example` in the Schema Object, but do not
define what deprecations means.  We also effectively deprecate
`allowEmptyValue` in the Parameter Object but did not explictly
say so.  We will likely make other deprecations in the future.

This defines a very basic deprecaton policy (they are still
supported, but we reserve the right to define a policy for
removing them in the future) and marks `allowEmptyValue` with
the same formatting used for `example`.
@handrews handrews requested review from a team as code owners May 16, 2025 01:04
@handrews handrews added clarification requests to clarify, but not change, part of the spec editorial Wording and stylistic issues labels May 16, 2025
@ralfhandl ralfhandl requested a review from a team May 16, 2025 17:29
@ralfhandl ralfhandl merged commit 4657cf5 into OAI:v3.2-dev May 19, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
clarification requests to clarify, but not change, part of the spec editorial Wording and stylistic issues
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants