rename `output.apply()` -> `output.applyOutput()` and `output.applyValue()` -> `output.apply()`
Open
Nobody has claimed this yet.
api/suggestion
area/languages
impact/breaking
kind/enhancement
- Dominant language
- Java
- Stars
- 85
- Forks
- 26
- Avg merge
- 11h 49m
- Merged PRs (30d)
- 22
Description
Hello!
- Vote on this issue by adding a 👍 reaction
- If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)
Issue details
public apply() -> T seems much more common than public apply() -> Output<T> from writing the docs.
curious to see the community's perspective on the default apply return type.
Affected area/feature
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 files, tests, or entry points are named. Review the public Output API and the eight-comment discussion before deciding whether the proposed method renames are accepted. Done means an agreed naming design, with all affected API references, tests, and documentation updated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100