Don't throw ApiFieldError when callable attribute's queryset is empty. #347
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I've had this same issue. Is this the best solution? |
|
Any progress on this? |
|
Okay, this isn't necessary for Fields where you can add null=True |
|
I'm looking through the example and I believe that the answer is to allow null=True if it's going to be empty. This combined with the other tickets about callables should fix it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is the simplest solution I found, it was taken from https://groups.google.com/group/django-tastypie/browse_thread/thread/e3e83c1db9b47a93
If there is a better way please advise, currently it seems that callable attributes are not usable without this fix.
Thanks.