Django rest framework pass field errors in the extra_kwargs dictionary
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
1
I am customizing the does_not_exist error message for a SlugField in my serializer as follows:
class PolicyCreateUpdateSerializer(serializers.ModelSerializer):
source_ip_group = serializers.SlugRelatedField(queryset=IPGroup.objects.all(), slug_field='name',
error_messages={"does_not_exist": "Custom"})
enabled = serializers.BooleanField()
class Meta:
model = Policy
fields = ['id', 'name', 'source_ip_group', 'enabled']
This works as expected.However, when I try to add this in the Meta attribute of the class, it does not work.
class PolicyCreateUpdateSerializer(serializers.ModelSerializer):
source_ip_group = serializers.SlugRelatedField(queryset=IPGroup.objects.all(), slug_field='name')
enabled = serializers.BooleanField()
class Meta:
model = Policy
fields = ['id', 'name', 'source_ip_group', 'enabled']
extra_kwargs = {'source_ip_group': {"error_messages": {"does_not_exist": "Custom"}}}
What am I doing wrong ?
python django django-rest-framework
asked Nov 23 '18 at 6:35
AmistadAmistad
2,83472640
add a comment |
1
I am customizing the does_not_exist error message for a SlugField in my serializer as follows:
class PolicyCreateUpdateSerializer(serializers.ModelSerializer):
source_ip_group = serializers.SlugRelatedField(queryset=IPGroup.objects.all(), slug_field='name',
error_messages={"does_not_exist": "Custom"})
enabled = serializers.BooleanField()
class Meta:
model = Policy
fields = ['id', 'name', 'source_ip_group', 'enabled']
This works as expected.However, when I try to add this in the Meta attribute of the class, it does not work.
class PolicyCreateUpdateSerializer(serializers.ModelSerializer):
source_ip_group = serializers.SlugRelatedField(queryset=IPGroup.objects.all(), slug_field='name')
enabled = serializers.BooleanField()
class Meta:
model = Policy
fields = ['id', 'name', 'source_ip_group', 'enabled']
extra_kwargs = {'source_ip_group': {"error_messages": {"does_not_exist": "Custom"}}}
What am I doing wrong ?
python django django-rest-framework
asked Nov 23 '18 at 6:35
AmistadAmistad
2,83472640
add a comment |
1
1
1
I am customizing the does_not_exist error message for a SlugField in my serializer as follows:
class PolicyCreateUpdateSerializer(serializers.ModelSerializer):
source_ip_group = serializers.SlugRelatedField(queryset=IPGroup.objects.all(), slug_field='name',
error_messages={"does_not_exist": "Custom"})
enabled = serializers.BooleanField()
class Meta:
model = Policy
fields = ['id', 'name', 'source_ip_group', 'enabled']
This works as expected.However, when I try to add this in the Meta attribute of the class, it does not work.
class PolicyCreateUpdateSerializer(serializers.ModelSerializer):
source_ip_group = serializers.SlugRelatedField(queryset=IPGroup.objects.all(), slug_field='name')
enabled = serializers.BooleanField()
class Meta:
model = Policy
fields = ['id', 'name', 'source_ip_group', 'enabled']
extra_kwargs = {'source_ip_group': {"error_messages": {"does_not_exist": "Custom"}}}
What am I doing wrong ?
python django django-rest-framework
asked Nov 23 '18 at 6:35
AmistadAmistad
2,83472640
I am customizing the does_not_exist error message for a SlugField in my serializer as follows:
class PolicyCreateUpdateSerializer(serializers.ModelSerializer):
source_ip_group = serializers.SlugRelatedField(queryset=IPGroup.objects.all(), slug_field='name',
error_messages={"does_not_exist": "Custom"})
enabled = serializers.BooleanField()
class Meta:
model = Policy
fields = ['id', 'name', 'source_ip_group', 'enabled']
This works as expected.However, when I try to add this in the Meta attribute of the class, it does not work.
class PolicyCreateUpdateSerializer(serializers.ModelSerializer):
source_ip_group = serializers.SlugRelatedField(queryset=IPGroup.objects.all(), slug_field='name')
enabled = serializers.BooleanField()
class Meta:
model = Policy
fields = ['id', 'name', 'source_ip_group', 'enabled']
extra_kwargs = {'source_ip_group': {"error_messages": {"does_not_exist": "Custom"}}}
What am I doing wrong ?
python django django-rest-framework
python django django-rest-framework
asked Nov 23 '18 at 6:35
AmistadAmistad
2,83472640
asked Nov 23 '18 at 6:35
AmistadAmistad
2,83472640
asked Nov 23 '18 at 6:35
AmistadAmistad
2,83472640
asked Nov 23 '18 at 6:35
AmistadAmistad
2,83472640
asked Nov 23 '18 at 6:35
AmistadAmistad
2,83472640
2,83472640
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
2
Mentioning the field explicitly will be used and will ignore any extra_kwargs for the field.
Ref: Serializer fields initialization
answered Nov 23 '18 at 8:35
SachinSachin
2,1351717
so there is no way that I can pass the extra_kwargs ?
– Amistad
Nov 23 '18 at 10:27
I think the logic is there to ignoreextra_kwargswhen declared field is used is because if you are declaring the field yourself, then you can mention all the things you require to override, whileextra_kwargsare there to override a piece of the field, not the whole thing.
– Sachin
Nov 23 '18 at 10:29
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
});
}
});
draft saved
draft discarded
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%2f53441675%2fdjango-rest-framework-pass-field-errors-in-the-extra-kwargs-dictionary%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
2
Mentioning the field explicitly will be used and will ignore any extra_kwargs for the field.
Ref: Serializer fields initialization
answered Nov 23 '18 at 8:35
SachinSachin
2,1351717
so there is no way that I can pass the extra_kwargs ?
– Amistad
Nov 23 '18 at 10:27
I think the logic is there to ignoreextra_kwargswhen declared field is used is because if you are declaring the field yourself, then you can mention all the things you require to override, whileextra_kwargsare there to override a piece of the field, not the whole thing.
– Sachin
Nov 23 '18 at 10:29
add a comment |
2
Mentioning the field explicitly will be used and will ignore any extra_kwargs for the field.
Ref: Serializer fields initialization
answered Nov 23 '18 at 8:35
SachinSachin
2,1351717
so there is no way that I can pass the extra_kwargs ?
– Amistad
Nov 23 '18 at 10:27
I think the logic is there to ignoreextra_kwargswhen declared field is used is because if you are declaring the field yourself, then you can mention all the things you require to override, whileextra_kwargsare there to override a piece of the field, not the whole thing.
– Sachin
Nov 23 '18 at 10:29
add a comment |
2
2
2
Mentioning the field explicitly will be used and will ignore any extra_kwargs for the field.
Ref: Serializer fields initialization
answered Nov 23 '18 at 8:35
SachinSachin
2,1351717
Mentioning the field explicitly will be used and will ignore any extra_kwargs for the field.
Ref: Serializer fields initialization
answered Nov 23 '18 at 8:35
SachinSachin
2,1351717
answered Nov 23 '18 at 8:35
SachinSachin
2,1351717
answered Nov 23 '18 at 8:35
SachinSachin
2,1351717
answered Nov 23 '18 at 8:35
SachinSachin
2,1351717
2,1351717
so there is no way that I can pass the extra_kwargs ?
– Amistad
Nov 23 '18 at 10:27
I think the logic is there to ignoreextra_kwargswhen declared field is used is because if you are declaring the field yourself, then you can mention all the things you require to override, whileextra_kwargsare there to override a piece of the field, not the whole thing.
– Sachin
Nov 23 '18 at 10:29
add a comment |
so there is no way that I can pass the extra_kwargs ?
– Amistad
Nov 23 '18 at 10:27
I think the logic is there to ignoreextra_kwargswhen declared field is used is because if you are declaring the field yourself, then you can mention all the things you require to override, whileextra_kwargsare there to override a piece of the field, not the whole thing.
– Sachin
Nov 23 '18 at 10:29
so there is no way that I can pass the extra_kwargs ?
– Amistad
Nov 23 '18 at 10:27
so there is no way that I can pass the extra_kwargs ?
– Amistad
Nov 23 '18 at 10:27
I think the logic is there to ignore
extra_kwargs when declared field is used is because if you are declaring the field yourself, then you can mention all the things you require to override, while extra_kwargs are there to override a piece of the field, not the whole thing.– Sachin
Nov 23 '18 at 10:29
I think the logic is there to ignore
extra_kwargs when declared field is used is because if you are declaring the field yourself, then you can mention all the things you require to override, while extra_kwargs are there to override a piece of the field, not the whole thing.– Sachin
Nov 23 '18 at 10:29
add a comment |
draft saved
draft discarded
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.
draft saved
draft discarded
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%2f53441675%2fdjango-rest-framework-pass-field-errors-in-the-extra-kwargs-dictionary%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
