[
https://issues.apache.org/jira/browse/HTTPCLIENT-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16986157#comment-16986157
]
Gary D. Gregory commented on HTTPCLIENT-2031:
---------------------------------------------
[~michael-o]
One reason I can think of keeping enums is for tools to enumerate (ah!) which
schemes we support. You can imaging, mapping these to command line optins or UI
elements like a drop down. So from that POV, it's a convenience. I'm not
hardcoded to the idea though. I'm OK for you to do as you best see fit
To address your custom concern, should we consider adding a CUSTOM enum value?
> Don't use plural names for enums
> --------------------------------
>
> Key: HTTPCLIENT-2031
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-2031
> Project: HttpComponents HttpClient
> Issue Type: Bug
> Components: HttpClient (async), HttpClient (classic)
> Affects Versions: 5.0 Beta6
> Reporter: Michael Osipov
> Assignee: Michael Osipov
> Priority: Major
>
> In Java world, the general concensus to have enum names to be singular, yes
> some of are in plural:
> {noformat}
> org.apache.hc.client5.http.async.methods.HttpRequests
> org.apache.hc.client5.http.async.methods.SimpleHttpRequests
> org.apache.hc.client5.http.auth.AuthSchemes
> org.apache.hc.client5.http.classic.methods.ClassicHttpRequests
> org.apache.hc.client5.http.cookie.CookieSpecs
> org.apache.hc.client5.http.impl.ChainElements
> {noformat}
> See also https://docs.oracle.com/javase/tutorial/java/javaOO/enum.html and
> https://stackoverflow.com/a/15756009/696632
> If no one objects ([~olegk], [~ggregory]), I will alter this on master.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org
For additional commands, e-mail: dev-h...@hc.apache.org
