![Sonos Abandons Streaming Device That Aimed to Rival Apple TV [Report]](https://www.iclarified.com/images/news/96703/96703/96703-640.jpg)
![HomePod With Display Delayed to Sync With iOS 19 Redesign [Kuo]](https://www.iclarified.com/images/news/96702/96702/96702-640.jpg)
![iPhone 17 Air to Measure 9.5mm Thick Including Camera Bar [Rumor]](https://www.iclarified.com/images/news/96699/96699/96699-640.jpg)
_Andrii_Yalanskyi_Alamy.jpg?#)
![[The AI Show Episode 139]: The Government Knows AGI Is Coming, Superintelligence Strategy, OpenAI’s $20,000 Per Month Agents & Top 100 Gen AI Apps](https://www.marketingaiinstitute.com/hubfs/ep%20139%20cover-2.png)
![[The AI Show Episode 138]: Introducing GPT-4.5, Claude 3.7 Sonnet, Alexa+, Deep Research Now in ChatGPT Plus & How AI Is Disrupting Writing](https://www.marketingaiinstitute.com/hubfs/ep%20138%20cover.png)
.png?width=1920&height=1920&fit=bounds&quality=80&format=jpg&auto=webp#)
-Rainbow-Six-Siege-X---Official-Gameplay-Trailer-00-01-00.png?width=1920&height=1920&fit=bounds&quality=80&format=jpg&auto=webp#)
Documenting properties
Suppose I have a property with an associated getter and setter (the property is not exposed directly) Where should I describe the property? The field javadoc The getter javadoc The setter javadoc Avoiding duplication would be nice (in case of any changes, I absolutely do not want to manually keep the two descriptions in sync). However, documenting a private field doesn't feel right.
Suppose I have a property with an associated getter and setter (the property is not exposed directly)
Where should I describe the property?
- The field javadoc
- The getter javadoc
- The setter javadoc
Avoiding duplication would be nice (in case of any changes, I absolutely do not want to manually keep the two descriptions in sync). However, documenting a private field doesn't feel right.
