Add update endpoint without primary for images #35

[asuresh-code]

Description

see #35

Testing instructions

Add a set up instructions describing how the reviewer should test the code

• Review code
• Check Actions build
• Review changes to test coverage
• {more steps here}

Agile board tracking

closes #35

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.88%. Comparing base (af5e70d) to head (d1be4a6).

Additional details and impacted files

@@             Coverage Diff             @@
##           develop      #75      +/-   ##
===========================================
+ Coverage    98.59%   98.88%   +0.28%     
===========================================
  Files           21       21              
  Lines          428      447      +19     
===========================================
+ Hits           422      442      +20     
+ Misses           6        5       -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[VKTB]

@asuresh-code Could you please resolve the conflicts?

[rowan04]

some comments, mainly on grammar and confusion

[rowan04]

When i tried it out, i tried to set ID as null, and whilst it didn't do it, it returned a 200 status code?

[asuresh-code]

When i tried it out, i tried to set ID as null, and whilst it didn't do it, it returned a 200 status code?

Was this on the docs on the localhost? I tried leaving the image_id blank (which is what I assume you mean by setting the ID to null) and it doesn't actually send a request (or get a response) , but it did show my previous response still (which was a successful response with a 200 code). This might be what's happening in your case as well? If you send an invalid response that gets a 404 response and then try setting the ID as null and do another request, I think it'll just display the previous 404 response.

[rowan04]

Was this on the docs on the localhost? I tried leaving the image_id blank (which is what I assume you mean by setting the ID to null) and it doesn't actually send a request (or get a response) , but it did show my previous response still (which was a successful response with a 200 code). This might be what's happening in your case as well? If you send an invalid response that gets a 404 response and then try setting the ID as null and do another request, I think it'll just display the previous 404 response.

Discussed with Anikesh in person. The actual topic here is when adding extra info to the request body, such as "id" or even a made up field, it gets included in the Curl response, but then these extra fields don't get expected or returned in the response body, and a 200 status code is returned.

[VKTB]

LGTM