hi I would like to ask something, I have a project I'm my teacher gave me to do in nestjs
This is a checkout app where I need to edit just the back,
currently I have my tables (tables, products, order) I have made my relationships etc.
I would like to add a means of payment (check, cash or card) and have it visible in order
I know what kind of relationship I am going to implement between the payment and order entity but I do not know how to implement the service so that it is visible in the invoice
#Nest registr app
wanton raft
brittle prism
Interesting you call it a "check out" app, because "check out" is only one process of a webshop. And, you make note of other processes of a webshop, like invoicing and ordering. So, is your project to build a webshop app or just a checkout process for a webshop app? Big difference in scope.
One of the first and probably one of the most important goals of a project or rather in managing a project is understanding the scope of the work, both overall for the project itself and for the individual tasks to complete the project, especially if you have deadlines to meet. 😉
wanton raft
Actually, I think it might be more accurate to call it check out process, to tell you the truth I don't fully understand everything . My teacher did the front and a par of the back, I made Every basic task la the relations between the entities and made my services, so everything works well, now I'd like to add specificity on the payment method like (cash, cheque etc) and the tables schemas cause now every tables have a specific position and I want differents dispositions for every rooms but I'm quite confuse on how to do it.
sorry to be vague, it's new to me , like I did it for one day and I already have a project on it
brittle prism
Do you need to have different inputs for each payment type? Or is it just value of the type of payment needed in the checkout? What is the goal of the project in terms of what you should be learning? Do you know that?
wanton raft
It a value value of the type of payment needed. the minimum objective of the application has been achieved because the application is running well and the data is in the database
now there are features to implement to go further which are those that I presented.
as for the objective of the course it was to manage data with mysql
brittle prism
Ah, ok. Well, if it is only a value, like from a picklist, you might want to just store the selected value in your order record.
wanton raft
yeah , but I'm a bit confuse on how to do it
brittle prism
To do what? Be specific. 🙂
wanton raft
ahaha I think I can't make it more clear than than what I said, sorry I don't how to word what I want to do
brittle prism
Maybe explain what you are confused about? My problem is, I don't know if it is how to do the frontend, the backend, the database, and I'm not going to explain making it happen for all of that.
I'm still fairly unsure about what you need too. You explaining what you are confused about might help me understand what you need too.
wanton raft
Well, the homework is to only work on the backend, that's what I did. Now I have to upgrade the app, like adding new features and what I confused about is if it'll drive me to touch the front or I can do all from the back
brittle prism
Well, depends on how the process works currently and where the payment type should come from.
wanton raft
when a client click to pay, I should have in my database which kind of payment he made, actually I don't know how to do it without touching the front
brittle prism
Yeah, usually the customer will select the payment type in the front end and it will change the process to get payment through that payment gateway (or put the order on hold, if it is bank transfer). So you are right. The user usually has to select the payment type.
wanton raft
thx