I have a say in this issue. All I have done this year is about shopping malls. Among them are from the shopping cart or product details page to the order confirmation page. I organize the data from the shopping cart according to the data format of the order confirmation page (usually into an object in the end) and then store it in localstorage (all done on the mobile side), and then jump directly to the page to traverse and render the data object on the order confirmation page. That's fine, don't worry, these are just for users to see on the front end. The backend will calculate the order amount again when paying, and then split the order, so even if the user changes the payment information, he still has to pay the money,
No, the shopping cart content is not transmitted from the form to the server. It depends on how your mall shopping cart is implemented. Whether it is SESSION, MySQL, or redis, etc. When the order is submitted, the shopping cart content needs to be on the server side, Here is to directly read the library or SESSION, redis Verify again whether the sku quantity is consistent when submitting it Recalculate the total price, discount, and total price on one side
Finally: Never trust the data submitted in the form, including the price of the product Otherwise, it will be a joke to buy thousands of yuan for just one penny.
Our previous approach was to integrate the data structure provided by the backend into a string, pass it to the backend, and the backend will parse it according to its own algorithm
For example1_xxx_24:2_xxx_56
This is the backend splitting into multiple products based on colons, and then getting the values of the three parameters based on underscores. The data at that time is, the order of the parameters cannot be wrong, and the parameters must be present,
Just an example, it depends on how you want to implement it in the backend, the frontend is only responsible for transmitting and receiving
Save the data in the shopping cart on the front end, such as vuex in VUE and redux in react. These data will always be stored in a public place. If you are not logged in, it doesn’t matter. Let him choose first in the shopping cart and click to pay. Log in again and finally submit it in the form of a json array
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
I have a say in this issue. All I have done this year is about shopping malls. Among them are from the shopping cart or product details page to the order confirmation page. I organize the data from the shopping cart according to the data format of the order confirmation page (usually into an object in the end) and then store it in localstorage (all done on the mobile side), and then jump directly to the page to traverse and render the data object on the order confirmation page. That's fine, don't worry, these are just for users to see on the front end. The backend will calculate the order amount again when paying, and then split the order, so even if the user changes the payment information, he still has to pay the money,
No, the shopping cart content is not transmitted from the form to the server. It depends on how your mall shopping cart is implemented.
Whether it is SESSION, MySQL, or redis, etc.
When the order is submitted, the shopping cart content needs to be on the server side,
Here is to directly read the library or SESSION, redis
Verify again whether the sku quantity is consistent when submitting it
Recalculate the total price, discount, and total price on one side
Finally: Never trust the data submitted in the form, including the price of the product
Otherwise, it will be a joke to buy thousands of yuan for just one penny.
Negotiate with your backend,
Our previous approach was to integrate the data structure provided by the backend into a string, pass it to the backend, and the backend will parse it according to its own algorithm
For example
1_xxx_24:2_xxx_56This is the backend splitting into multiple products based on colons, and then getting the values of the three parameters based on underscores. The data at that time is, the order of the parameters cannot be wrong, and the parameters must be present,
Just an example, it depends on how you want to implement it in the backend, the frontend is only responsible for transmitting and receiving
Save the data in the shopping cart on the front end, such as vuex in VUE and redux in react. These data will always be stored in a public place. If you are not logged in, it doesn’t matter. Let him choose first in the shopping cart and click to pay. Log in again and finally submit it in the form of a json array