Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Field with encrypt_key display field value in __repr__ and log as default #108
When a field has an encrypt_key, its value is unreadable without the key used for encryption on the database table.
Not sure if it's a bug as that behavior can be bypassed easily adding convenient repr and/or str to a model.
What do you think ?
If we consider that its developer responsability to deal with the repr of the model, I'm okay with that and I can write a section into documentation.
So, my 2cts, I guess the best world would be an option to let the dev choose using a lazy decript or not !