swagger-api / swagger-api/swagger-core
If a property has no annotation, but only a getter, it should be read-only.
Open
Nobody has claimed this yet.
backlog
- Dominant language
- Java
- Stars
- 7.5k
- Forks
- 2.3k
- Avg merge
- 18h 1m
- Merged PRs (30d)
- 10
Description
If a property has no annotation, but only a getter, it should be read-only.
For example.
public class Cap {
public String getBrand() {
return "no brand";
}
}
A Cap's property "brand" should be read-only. Because there's no way to write "brand".
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, test, or entry point is named. Start by locating the Java property/schema generation logic for getter-only properties, then verify that a property with only a getter is emitted as read-only and that writable properties remain unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100