Laravel: form method != save method?
I am new to Laravel coming from CakePHP where the form and save method for a form is one and the same function name. I saw in many Laravel tutorials that the from method (that displays the form) is different than the method to save form (that actually saves data). Why using 2 different method names?
For example what's wrong with:
pub function xyz(Request $request)
{
if($results->isMethod('post'))
... then save and return redirect
... the code for showing the form in case there is no POST.
then having 2 routes one for GET and one for POST on the same url?
laravel forms save
asked Nov 13 '18 at 4:19
Vlad AgriVlad Agri
1715
add a comment |
I am new to Laravel coming from CakePHP where the form and save method for a form is one and the same function name. I saw in many Laravel tutorials that the from method (that displays the form) is different than the method to save form (that actually saves data). Why using 2 different method names?
For example what's wrong with:
pub function xyz(Request $request)
{
if($results->isMethod('post'))
... then save and return redirect
... the code for showing the form in case there is no POST.
then having 2 routes one for GET and one for POST on the same url?
laravel forms save
asked Nov 13 '18 at 4:19
Vlad AgriVlad Agri
1715
add a comment |
I am new to Laravel coming from CakePHP where the form and save method for a form is one and the same function name. I saw in many Laravel tutorials that the from method (that displays the form) is different than the method to save form (that actually saves data). Why using 2 different method names?
For example what's wrong with:
pub function xyz(Request $request)
{
if($results->isMethod('post'))
... then save and return redirect
... the code for showing the form in case there is no POST.
then having 2 routes one for GET and one for POST on the same url?
laravel forms save
asked Nov 13 '18 at 4:19
Vlad AgriVlad Agri
1715
I am new to Laravel coming from CakePHP where the form and save method for a form is one and the same function name. I saw in many Laravel tutorials that the from method (that displays the form) is different than the method to save form (that actually saves data). Why using 2 different method names?
For example what's wrong with:
pub function xyz(Request $request)
{
if($results->isMethod('post'))
... then save and return redirect
... the code for showing the form in case there is no POST.
then having 2 routes one for GET and one for POST on the same url?
laravel forms save
laravel forms save
asked Nov 13 '18 at 4:19
Vlad AgriVlad Agri
1715
asked Nov 13 '18 at 4:19
Vlad AgriVlad Agri
1715
asked Nov 13 '18 at 4:19
Vlad AgriVlad Agri
1715
asked Nov 13 '18 at 4:19
Vlad AgriVlad Agri
1715
asked Nov 13 '18 at 4:19
Vlad AgriVlad Agri
1715
1715
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
It is because people like to filter out things at route level not in controller, Also it helps developer to apply middleware grouping for each route separately. so that they can apply roles and permission etc. easily at route level.
It will looks horrible if mix all things in controller.
Think about middleware and groups in your code.
answered Nov 13 '18 at 4:34
C2486C2486
19.1k32767
now it makes sense, thanks
– Vlad Agri
Nov 13 '18 at 17:08
add a comment |
It is because you don't wanna mix a lot of logic in the same method . The case you have simple is the simple scenario . But there will be case where you wanna pass initial data in the create form . You have to write logic for that also in the same method and while you store the data you need to do the validation and calculate other business logic . If you combine all those things in one method it will mix all the things in one method and code difficult to read
answered Nov 13 '18 at 4:41
ashok poudelashok poudel
151113
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53273750%2flaravel-form-method-save-method%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
It is because people like to filter out things at route level not in controller, Also it helps developer to apply middleware grouping for each route separately. so that they can apply roles and permission etc. easily at route level.
It will looks horrible if mix all things in controller.
Think about middleware and groups in your code.
answered Nov 13 '18 at 4:34
C2486C2486
19.1k32767
now it makes sense, thanks
– Vlad Agri
Nov 13 '18 at 17:08
add a comment |
It is because people like to filter out things at route level not in controller, Also it helps developer to apply middleware grouping for each route separately. so that they can apply roles and permission etc. easily at route level.
It will looks horrible if mix all things in controller.
Think about middleware and groups in your code.
answered Nov 13 '18 at 4:34
C2486C2486
19.1k32767
now it makes sense, thanks
– Vlad Agri
Nov 13 '18 at 17:08
add a comment |
It is because people like to filter out things at route level not in controller, Also it helps developer to apply middleware grouping for each route separately. so that they can apply roles and permission etc. easily at route level.
It will looks horrible if mix all things in controller.
Think about middleware and groups in your code.
answered Nov 13 '18 at 4:34
C2486C2486
19.1k32767
It is because people like to filter out things at route level not in controller, Also it helps developer to apply middleware grouping for each route separately. so that they can apply roles and permission etc. easily at route level.
It will looks horrible if mix all things in controller.
Think about middleware and groups in your code.
answered Nov 13 '18 at 4:34
C2486C2486
19.1k32767
answered Nov 13 '18 at 4:34
C2486C2486
19.1k32767
answered Nov 13 '18 at 4:34
C2486C2486
19.1k32767
answered Nov 13 '18 at 4:34
C2486C2486
19.1k32767
19.1k32767
now it makes sense, thanks
– Vlad Agri
Nov 13 '18 at 17:08
add a comment |
now it makes sense, thanks
– Vlad Agri
Nov 13 '18 at 17:08
now it makes sense, thanks
– Vlad Agri
Nov 13 '18 at 17:08
now it makes sense, thanks
– Vlad Agri
Nov 13 '18 at 17:08
add a comment |
It is because you don't wanna mix a lot of logic in the same method . The case you have simple is the simple scenario . But there will be case where you wanna pass initial data in the create form . You have to write logic for that also in the same method and while you store the data you need to do the validation and calculate other business logic . If you combine all those things in one method it will mix all the things in one method and code difficult to read
answered Nov 13 '18 at 4:41
ashok poudelashok poudel
151113
add a comment |
It is because you don't wanna mix a lot of logic in the same method . The case you have simple is the simple scenario . But there will be case where you wanna pass initial data in the create form . You have to write logic for that also in the same method and while you store the data you need to do the validation and calculate other business logic . If you combine all those things in one method it will mix all the things in one method and code difficult to read
answered Nov 13 '18 at 4:41
ashok poudelashok poudel
151113
add a comment |
It is because you don't wanna mix a lot of logic in the same method . The case you have simple is the simple scenario . But there will be case where you wanna pass initial data in the create form . You have to write logic for that also in the same method and while you store the data you need to do the validation and calculate other business logic . If you combine all those things in one method it will mix all the things in one method and code difficult to read
answered Nov 13 '18 at 4:41
ashok poudelashok poudel
151113
It is because you don't wanna mix a lot of logic in the same method . The case you have simple is the simple scenario . But there will be case where you wanna pass initial data in the create form . You have to write logic for that also in the same method and while you store the data you need to do the validation and calculate other business logic . If you combine all those things in one method it will mix all the things in one method and code difficult to read
answered Nov 13 '18 at 4:41
ashok poudelashok poudel
151113
answered Nov 13 '18 at 4:41
ashok poudelashok poudel
151113
answered Nov 13 '18 at 4:41
ashok poudelashok poudel
151113
answered Nov 13 '18 at 4:41
ashok poudelashok poudel
151113
151113
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53273750%2flaravel-form-method-save-method%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
