Closed carltonwhitehead closed 9 years ago
@carltonwhitehead thoughts on changing the REST URIs from camelcase to underscore separated? I realized I haven't worked with a REST API with camelcase URIs and I checked out twitter, dropbox, google maps, etsy and they all use underscores.
What do we stand to gain/lose by changing to underscores vs not changing? "other people do it this way" doesn't seem like a strong justification for change. According to RFC 2616, the relevant part of the URI is case sensitive, so having them in camel case isn't going to break HTTP specs or introduce some unpredictable behavior. When we get the API spec generator up and running, it'll be clear to anyone using what the case will be.
Nothing to gain/lose other than effectively following a 'styleguide' but with respect to URI format.
@carltonwhitehead Thoughts on handicapFactor type and constraints. Right now I have it as BigDecimal and constrained between 0 and 1.
BigDecimal from 0 to 1 seems like a good fit.
add a handicap group