Level 104
Separate controllers for each resource.
... cards??? Not credit cards???
Dec 11, 2019
18
Level 11
api controller
I have a system contain users, customers, companies, cards and items. Should I make everyone of them independent API Controller to prevent mistakes or I make one API Controller to all of them
Level 11
yeah credit cards
Level 104
Can you tell me the name of this application that I should know to avoid??
Level 11
why ?? can you tell me ??
Level 104
You are going to store user's credit card details in your database.
Level 11
because it's a bank application
Level 51
You have been hired by a bank to create an API for applications that consume credit card numbers?
I must know more about this bank?
Level 104
Is this a real application, or something you are doing as a personal project that will never be used publicly?
If you are building a real world application, then you need to take so advice regarding accepting and storing credit card and personal information belonging to users.
Level 11
I'd love to. It will be so useful to me all the advises
Level 11
No I'm not hired by a bank it's some project I'm working on it and I hope to make it well
Level 104
Ok, my advice is don't accept and store credit card numbers on your own servers
Level 11
Ok so how you suggest to do it in the right way ????
Level 21
Stipe or similar
Level 8
Yes, you probably want separate controllers for each of these. It's likely that you will only end up calling two or three end points from a page (I'm guessing your are using vue or some sort of SPA) at the same time. Which isn't too much of a problem.
If you do end up making lots and lots of calls at the same time, then you may want to consider some sort of facade controller.
I would also recommend reading up on REST apis. May also be worth checking to see if there is anything on laracasts video section about creating apis. I'm pretty sure there will be.
Level 1
As everybody said, do make a separate controller for each, it is referred to as end-point.
users, customers, companies, and items are all valid end-points to have.
There is no reason to ever have an end-point for cards, unless you are working as a financial institution and building an app that does that. Better leave it out of tests system/project as well.
It would be far better to try Stripe / PayPal or any other payment gateway, almost all of them provide a testing system.
Level 61
Level 11
Schema::create('salaries', function (Blueprint $table) { $table->bigIncrements('id')->primary(); $table->string('init_salary'); $table->string('ssn'); $table->string('assurance_mount'); $table->string('bounces'); $table->string('bounce_type'); $table->string('deductions'); $table->string('deduct_type'); $table->string('total_salary'); $table->timestamp('paid_at'); $table->timestamps(); });
can you help me with that please ???
Level 21
Are you getting any errors?
Please or to participate in this conversation.