#django

fub: well they do this even more professional. I should call those functions

HyP3r: :D

I'm trying to learn django rest framework and I'm having trouble passing in extra fields along with data to the ModelSerializer

I have a model that has two fields

One is being passed in the call to the api

the other is calculated in the view

But I can't figure out how to get that into the serializer before calling .is_valid()

would love to help but I've never used DRF

have you asked in #restframework ?

I'll try over there

ljolly: serializers also take a context

@moldy I tried to use context to pass it in https://gobin.io/YWxZ

but after running is_valid()

short_id is still not set

ljolly: well, you still need to pass the short_id to the serializer from wherever you call it. we don't see that code.

*to the serializer context

This is what I'm running to test it https://gobin.io/HSGS

is_valid() works

but when I run save

The model validation throughs this error: {'short_id': ['This field cannot be blank.', 'only a-zA-Z0-9 valid chars and max length of 12']}

throws*

this is my model code if that is needed https://gobin.io/TNyT

mmmh, I do have idea though...

oops

switched rooms...

ljolly: your get_short_id() method returns NOne

So yeah, I run that and it seems that short_id is empty when it gets to the model validator

indeed it does...

some languages return the last expression in a function, python is not one of them ;) you probably need to say `return self.context.get("short_id")`

Haven't used python in a few years and while trying to relearn it I'm also trying to learn django and rest-framework at the same time.

After working at it for several hours I find myself mixing in ruby or go code :P

alright, there's still something else wrong

I added a return to that https://gobin.io/wfmk

It's still empty somehow

in nap you'd just use a context_field ...

:P

So get_short_id is the serializer isn't getting called at all

I raised an error in it

and it never threw

maybe you need to add it to fields explicitly, not sure

__all__ is mostly an anti-pattern imho

+1

was bitten by that more than once on this project

"Why did it all blow up? FileField is not JSON serialisable! Oh, shit, I added a new field..."

good thing nap Mappers are inheritable :)

hehe ya