Configure ActiveResource::Base.casing
#421
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
Base.casing
configuration controls how resource classes handle API responses with cases that differ from Ruby'scamel_case
idioms.For example, setting
casing = :camelcase
will configure the resource to transform inbound camelCase JSON to under_score when loading API data:Similarly, the casing configures the resource to transform outbound attributes from the intermediate
under_score
idiomatic Ruby names to the originalcamelCase
names:By default, resources are configured with
casing = :none
, which does not transform keys. In addition to:none
and:camelcase
, the:underscore
configuration ensures idiomatic Ruby names throughout.When left unconfigured,
casing = :camelcase
will transform keys with a lower case first letter. To transform with upper case letters, construct an instance ofActiveResource::Casings::CamelcaseCasing
:Casing transformations are also applied to query parameters built from
.where
clauses: