Update default accuracy to None to support null JSON values

[sahil-R]

Fixes

Fixes #674 by @dhruvkb

Description

The issue stated that the serializers were not allowing null values to be passed on in the response JSON which is returned by the API,The code was running fine when tested however the accuracy were not accompanied with the tags which were added to the response,added the fix with default accuracy as None and edited the test cases for the same.

Testing Instructions

just do any API request and the output runs fine as usual with null values returned as well.

Checklist

• My pull request has a descriptive title (not a vague title like Update index.md).
• My pull request targets the default branch of the repository (main) or a parent feature branch.
• My commit messages follow best practices.
• My code follows the established code style of the repository.
• I added or updated tests for the changes I made (if applicable).
• I added or updated documentation (if applicable).
• I tried running the project locally and verified that there are no visible errors.

Developer Certificate of Origin

Developer Certificate of Origin

Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.


Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

[dhruvkb]

Please remove the root Pipfile and Pipfile.lock. Both the api/ and ingestion_server/ have their Python environments in their directories.

[dhruvkb]

This is looking good now, thanks @sahil-R!

[sahil-R]

This is looking good now, thanks @sahil-R!

Hey @dhruvkb , Thank you for the update, can you suggest me another approver for these changes since it requires two approvals.

[dhruvkb]

I tagged @WordPress/openverse-api on this issue, which picked @AetherUnbound as the second reviewer.

[AetherUnbound]

Thanks for the contribution @sahil-R! This looks good and can be merged as soon as we update the help text.