Java
108 строк · 3.9 Кб
1name: Feature Enhancement Request2description: I want to make an existing feature better3labels: ["type=enhancement"]4body:5- type: markdown6attributes:7value: >8Filing feature requests is one of the most popular ways to contribute to Guava.
9
10
11Be aware, though: most feature requests are not accepted, even if they're suggested by12a full-time Guava team member. [Feedback](https://stackoverflow.com/a/4543114) from our13users indicates that they really appreciate Guava's high power-to-weight ratio. It's14important to us to keep Guava as easy to use and understand as we can. That means boiling
15features down to compact but powerful abstractions, and controlling feature bloat carefully.16
17- type: textarea18attributes:19label: API(s)20description: Which existing classes or methods do you want to improve?21placeholder: e.g., `com.google.common.collect.ImmutableList::of`22render: java23validations:24required: true25
26- type: textarea27attributes:28label: How do you want it to be improved?29validations:30required: true31
32- type: textarea33attributes:34label: Why do we need it to be improved?35validations:36required: true37
38- type: textarea39attributes:40label: Example41description: >42Please provide an example usage of the feature that would be different with the improvement.
43render: java44validations:45required: true46
47- type: textarea48attributes:49label: Current Behavior50description: What does the feature currently do?51validations:52required: true53
54- type: textarea55attributes:56label: Desired Behavior57description: What do you want it to do instead?58validations:59required: true60
61- type: markdown62attributes:63value: >64Did you *actually* encounter the need for this enhancement in a real-world scenario, or does
65it just seem like a sensible behavior for the feature to have?
66
67
68Before we make significant changes to existing features in Guava, we really want to be sure69that it's for a use case that actually comes up in the real world. We want to hear the
70real-world use case so the community can discuss and debate whether this feature is actually71the *best* way to address the real use case, or whether or not a different approach might be72more appropriate.
73
74
75It's okay if you can't provide complete context on a use case. We understand if you are not
76able to discuss the full details of what you're working on.
77
78
79But Guava aims to provide functionality that is useful across boundaries of projects,80companies, or even industries — utilities useful for a sizable proportion of all Java81programmers everywhere. If you can give enough detail such that any of us can imagine coming
82across a similar need in our own work, that's extremely helpful in studying how broadly83useful the proposed change will be.
84
85- type: textarea86attributes:87label: Concrete Use Cases88description: Please provide use cases that actually came up in the real world.89validations:90required: true91
92- type: checkboxes93attributes:94label: Checklist95options:96- label: >97I agree to follow the
98[code of conduct](https://github.com/google/.github/blob/master/CODE_OF_CONDUCT.md).
99required: true100- label: >101I have read and understood the [contribution
102guidelines](https://github.com/google/guava/wiki/HowToContribute#feature-requests).
103required: true104- label: >105I have read and understood
106[Guava's philosophy](https://github.com/google/guava/wiki/PhilosophyExplained), and
107I strongly believe that this proposal aligns with it.
108required: true109