You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Oct 3, 2019. It is now read-only.
MipApplication's model is populated using Microbadger's API using the pre_save method. How is it possible to handle a non-existent image and trigger an error?
This part of the logic might have to be moved into the serializer. It's a good idea if the API is called only when the instance needs to be updated or created. Otherwise performances will be affected. It looks like it's only called on creation and update: http://www.django-rest-framework.org/api-guide/serializers/#validation
The text was updated successfully, but these errors were encountered:
Also think about making tests at the API level to ensure that the API always answer with a valid HTTP status and the MicrobadgerService does not slows it down too much (thinking about trying to push a non-existent docker image or an image that has been indexed in MicroBadger yet).
How to handle the cases where the image has not been indexed by MicroBadger?
MipApplication's model is populated using Microbadger's API using the
pre_save
method. How is it possible to handle a non-existent image and trigger an error?This part of the logic might have to be moved into the serializer. It's a good idea if the API is called only when the instance needs to be updated or created. Otherwise performances will be affected. It looks like it's only called on creation and update: http://www.django-rest-framework.org/api-guide/serializers/#validation
The text was updated successfully, but these errors were encountered: