refactor: remove the console expressions

It is considered a best practice to avoid the use of any `console` methods in JavaScript code that will run on the browser.

**NOTE:** If your repository contains a server side project, you can add `"nodejs"` to the `environment` property of analyzer meta in `.deepsource.toml`.
This will prevent this issue from getting raised.
Documentation for the analyzer meta can be found [here](https://docs.deepsource.com/docs/analyzers-javascript#meta).
Alternatively, you can silence this issue for your repository [as shown here](https://deepsource.com/blog/releases-issue-actions).

If a specific `console` call is meant to stay for other reasons, you can add [a skipcq comment](https://docs.deepsource.com/docs/issues-ignore-rules#silencing-a-specific-issue) to that line.
This will inform other developers about the reason behind the log's presence, and prevent DeepSource from flagging it.
This commit is contained in:
deepsource-autofix[bot] 2024-05-06 11:34:41 +00:00 committed by GitHub
parent f17ea51c01
commit e0969ae66f
No known key found for this signature in database
GPG key ID: B5690EEEBB952194

View file

@ -130,7 +130,7 @@ export async function postVerifyCart(
Object.entries(currentCartData).forEach(([uuid, currentData]) => {
verifiedItems.forEach((verifiedItem: Item) => {
if (verifiedItem.uuid === uuid) {
console.log(verifiedItem, uuid);
newCartData[uuid] = {
amount: currentData.amount,
data: verifiedItem,