swagger-api / swagger-api/swagger-core
Like to propose a new property to set Future ,UpComing ,InNextRelease something to represent API specification to showcase user what they can expect in next release
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 7.5k
- Forks
- 2.3k
- Avg merge
- 18h 1m
- Merged PRs (30d)
- 10
Description
Like to propose a new property to set Future ,UpComing ,InNextRelease something to represent API specification to showcase user what they can expect in next release .
just to opposite of deprecated which will be removed the propose is something what API is expected in future not completely working now or in Draft
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is identified. Start by reviewing how swagger-core represents deprecated API elements and the relevant OpenAPI specification metadata, then clarify the proposed lifecycle property and its expected semantics. Done would require an agreed specification and implementation scope, with tests covering the new representation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, openapi
- Domain
- api, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100