Feat: save approved review

[lariciamota]

What problem is this solving?

The approved info on the request body for creating a new review was being ignored, so even when it was sent as true the review was being saved as false.

How to test it?

Workspace laricia

Through the /review route: POST https://laricia--storeframework.myvtex.com/reviews-and-ratings/api/review
Body with approved as true:

{
    "productId": "21395412",
    "rating": 4,
    "title": "Review Title",
    "text": "Review Text",
    "reviewerName": "Reviewer Name",
    "approved": true
}

⚠️ Remember to use the header VtexIdclientAutCookie with your token when testing the route.

Screenshots or example usage:

Sending the POST req:

Checking that it was saved as true:

Ref

• Jira task

[vtex-io-ci-cd]

Hi! I'm VTEX IO CI/CD Bot and I'll be helping you to publish your app! 🤖

Please select which version do you want to release:

• Patch (backwards-compatible bug fixes)

• Minor (backwards-compatible functionality)

• Major (incompatible API changes)

And then you just need to merge your PR when you are ready! There is no need to create a release commit/tag.

• No thanks, I would rather do it manually 😞

[vtex-io-docs-bot]

Beep boop 🤖

I noticed you didn't make any changes at the docs/ folder

• There's nothing new to document 🤔
• I'll do it later 😞

In order to keep track, I'll create an issue if you decide now is not a good time

• I just updated 🎉🎉

The base branch was changed.

[github-actions]

	Messages
📖	❤️ Thanks!
📖	🎉 PR additions = 6, PR deletions = 1

Generated by 🚫 dangerJS against 7ee8160

[vtex-io-ci-cd]

Your PR has been merged! App is being published. 🚀
Version 3.16.1 → 3.17.0

After the publishing process has been completed (check #vtex-io-releases) and doing A/B tests with the new version, you can deploy your release by running:

vtex deploy [email protected]

After that your app will be updated on all accounts.

For more information on the deployment process check the docs. 📖