ActiveModel Serializer JSON Includes “attributes” Key
I'm using the Rails ActiveModel Serializer to output JSON to an API endpoint.
I'm getting this JSON output:
{
"data":[
{
"id":"396",
"type":"profiles",
"attributes":{
"name":"Impossibles",
"created-at":"2017-05-11T18:14:06.201-04:00",
"updated-at":"2018-04-01T13:34:15.905-04:00",
"website":"http://soundcloud.com/impossibles"
}
}
]
}
But was expecting it to be formatted like this:
{
"data":[
{
"id":"396",
"type":"profiles",
"name":"Impossibles",
"created-at":"2017-05-11T18:14:06.201-04:00",
"updated-at":"2018-04-01T13:34:15.905-04:00",
"website":"http://soundcloud.com/impossibles"
}
]
}
Trying to avoid the extra level of nesting in the returned JSON.
Is there a way to remove the "attributes" key?
This is my serializer:
class ProfileSerializer < ActiveModel::Serializer
attributes :id, :name, :created_at, :updated_at, :website
end
And my controller:
def show
profile = Profile.find(params[:id])
render json: profile, status: :ok
end
ruby-on-rails json ruby serialization
asked Dec 30 '18 at 4:13
coryetzkorncoryetzkorn
4061619
add a comment |
I'm using the Rails ActiveModel Serializer to output JSON to an API endpoint.
I'm getting this JSON output:
{
"data":[
{
"id":"396",
"type":"profiles",
"attributes":{
"name":"Impossibles",
"created-at":"2017-05-11T18:14:06.201-04:00",
"updated-at":"2018-04-01T13:34:15.905-04:00",
"website":"http://soundcloud.com/impossibles"
}
}
]
}
But was expecting it to be formatted like this:
{
"data":[
{
"id":"396",
"type":"profiles",
"name":"Impossibles",
"created-at":"2017-05-11T18:14:06.201-04:00",
"updated-at":"2018-04-01T13:34:15.905-04:00",
"website":"http://soundcloud.com/impossibles"
}
]
}
Trying to avoid the extra level of nesting in the returned JSON.
Is there a way to remove the "attributes" key?
This is my serializer:
class ProfileSerializer < ActiveModel::Serializer
attributes :id, :name, :created_at, :updated_at, :website
end
And my controller:
def show
profile = Profile.find(params[:id])
render json: profile, status: :ok
end
ruby-on-rails json ruby serialization
asked Dec 30 '18 at 4:13
coryetzkorncoryetzkorn
4061619
add a comment |
I'm using the Rails ActiveModel Serializer to output JSON to an API endpoint.
I'm getting this JSON output:
{
"data":[
{
"id":"396",
"type":"profiles",
"attributes":{
"name":"Impossibles",
"created-at":"2017-05-11T18:14:06.201-04:00",
"updated-at":"2018-04-01T13:34:15.905-04:00",
"website":"http://soundcloud.com/impossibles"
}
}
]
}
But was expecting it to be formatted like this:
{
"data":[
{
"id":"396",
"type":"profiles",
"name":"Impossibles",
"created-at":"2017-05-11T18:14:06.201-04:00",
"updated-at":"2018-04-01T13:34:15.905-04:00",
"website":"http://soundcloud.com/impossibles"
}
]
}
Trying to avoid the extra level of nesting in the returned JSON.
Is there a way to remove the "attributes" key?
This is my serializer:
class ProfileSerializer < ActiveModel::Serializer
attributes :id, :name, :created_at, :updated_at, :website
end
And my controller:
def show
profile = Profile.find(params[:id])
render json: profile, status: :ok
end
ruby-on-rails json ruby serialization
asked Dec 30 '18 at 4:13
coryetzkorncoryetzkorn
4061619
I'm using the Rails ActiveModel Serializer to output JSON to an API endpoint.
I'm getting this JSON output:
{
"data":[
{
"id":"396",
"type":"profiles",
"attributes":{
"name":"Impossibles",
"created-at":"2017-05-11T18:14:06.201-04:00",
"updated-at":"2018-04-01T13:34:15.905-04:00",
"website":"http://soundcloud.com/impossibles"
}
}
]
}
But was expecting it to be formatted like this:
{
"data":[
{
"id":"396",
"type":"profiles",
"name":"Impossibles",
"created-at":"2017-05-11T18:14:06.201-04:00",
"updated-at":"2018-04-01T13:34:15.905-04:00",
"website":"http://soundcloud.com/impossibles"
}
]
}
Trying to avoid the extra level of nesting in the returned JSON.
Is there a way to remove the "attributes" key?
This is my serializer:
class ProfileSerializer < ActiveModel::Serializer
attributes :id, :name, :created_at, :updated_at, :website
end
And my controller:
def show
profile = Profile.find(params[:id])
render json: profile, status: :ok
end
ruby-on-rails json ruby serialization
ruby-on-rails json ruby serialization
asked Dec 30 '18 at 4:13
coryetzkorncoryetzkorn
4061619
asked Dec 30 '18 at 4:13
coryetzkorncoryetzkorn
4061619
asked Dec 30 '18 at 4:13
coryetzkorncoryetzkorn
4061619
asked Dec 30 '18 at 4:13
coryetzkorncoryetzkorn
4061619
asked Dec 30 '18 at 4:13
coryetzkorncoryetzkorn
4061619
4061619
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
After reading through some GitHub issues, it appears the "attributes" nesting is coming from the JSON API spec and is expected behavior:
https://jsonapi.org/format/#document-resource-objects
This issue was helpful:
https://github.com/rails-api/active_model_serializers/issues/2202
Looks like a feature, not a bug.
answered Dec 30 '18 at 4:25
coryetzkorncoryetzkorn
4061619
1
If you don't want to conform to JSON API specification, you can always change your adapter tojson, see here.
– Marcin Kołodziej
Dec 30 '18 at 4:59
@MarcinKołodziej thanks! Didn't realize there were two JSON adapters.
– coryetzkorn
Jan 2 at 14:52
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53975225%2factivemodel-serializer-json-includes-attributes-key%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
After reading through some GitHub issues, it appears the "attributes" nesting is coming from the JSON API spec and is expected behavior:
https://jsonapi.org/format/#document-resource-objects
This issue was helpful:
https://github.com/rails-api/active_model_serializers/issues/2202
Looks like a feature, not a bug.
answered Dec 30 '18 at 4:25
coryetzkorncoryetzkorn
4061619
1
If you don't want to conform to JSON API specification, you can always change your adapter tojson, see here.
– Marcin Kołodziej
Dec 30 '18 at 4:59
@MarcinKołodziej thanks! Didn't realize there were two JSON adapters.
– coryetzkorn
Jan 2 at 14:52
add a comment |
After reading through some GitHub issues, it appears the "attributes" nesting is coming from the JSON API spec and is expected behavior:
https://jsonapi.org/format/#document-resource-objects
This issue was helpful:
https://github.com/rails-api/active_model_serializers/issues/2202
Looks like a feature, not a bug.
answered Dec 30 '18 at 4:25
coryetzkorncoryetzkorn
4061619
1
If you don't want to conform to JSON API specification, you can always change your adapter tojson, see here.
– Marcin Kołodziej
Dec 30 '18 at 4:59
@MarcinKołodziej thanks! Didn't realize there were two JSON adapters.
– coryetzkorn
Jan 2 at 14:52
add a comment |
After reading through some GitHub issues, it appears the "attributes" nesting is coming from the JSON API spec and is expected behavior:
https://jsonapi.org/format/#document-resource-objects
This issue was helpful:
https://github.com/rails-api/active_model_serializers/issues/2202
Looks like a feature, not a bug.
answered Dec 30 '18 at 4:25
coryetzkorncoryetzkorn
4061619
After reading through some GitHub issues, it appears the "attributes" nesting is coming from the JSON API spec and is expected behavior:
https://jsonapi.org/format/#document-resource-objects
This issue was helpful:
https://github.com/rails-api/active_model_serializers/issues/2202
Looks like a feature, not a bug.
answered Dec 30 '18 at 4:25
coryetzkorncoryetzkorn
4061619
answered Dec 30 '18 at 4:25
coryetzkorncoryetzkorn
4061619
answered Dec 30 '18 at 4:25
coryetzkorncoryetzkorn
4061619
answered Dec 30 '18 at 4:25
coryetzkorncoryetzkorn
4061619
4061619
1
If you don't want to conform to JSON API specification, you can always change your adapter tojson, see here.
– Marcin Kołodziej
Dec 30 '18 at 4:59
@MarcinKołodziej thanks! Didn't realize there were two JSON adapters.
– coryetzkorn
Jan 2 at 14:52
add a comment |
1
If you don't want to conform to JSON API specification, you can always change your adapter tojson, see here.
– Marcin Kołodziej
Dec 30 '18 at 4:59
@MarcinKołodziej thanks! Didn't realize there were two JSON adapters.
– coryetzkorn
Jan 2 at 14:52
1
1
If you don't want to conform to JSON API specification, you can always change your adapter to
json, see here.– Marcin Kołodziej
Dec 30 '18 at 4:59
If you don't want to conform to JSON API specification, you can always change your adapter to
json, see here.– Marcin Kołodziej
Dec 30 '18 at 4:59
@MarcinKołodziej thanks! Didn't realize there were two JSON adapters.
– coryetzkorn
Jan 2 at 14:52
@MarcinKołodziej thanks! Didn't realize there were two JSON adapters.
– coryetzkorn
Jan 2 at 14:52
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53975225%2factivemodel-serializer-json-includes-attributes-key%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
