Allow imageURLField to be imported dynamically #376
Conversation
This file contains hidden or 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
samar-hassan
requested changes
Sep 1, 2025
oscarapi/serializers/utils.py
Outdated
|
|
||
| from oscarapi.utils.exists import construct_id_filter | ||
| from .fields import ImageUrlField | ||
| from oscarapi.utils.loading import get_api_classes |
Contributor
There was a problem hiding this comment.
please use get_api_class
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 change will be it convenient to further customize
ImageUrlFieldin thecustomapp.serializers.fieldsclass. With the initial setup this was not possible since teh changed areas hard coded importImageUrlFieldfromoscarapi.fieldsinstead of using the dynamic importget_api_classmethod.