Why Laravel Resource Create and Edit operations are depicted using GET












1














I am picking up on Laravel, and noted that on Laravel's Documentation, it states that the the GET HTTP verb will be handled by the create and edit operations, but from my understanding of REST and CRUD, a create or edit operation actually results in change of records or state on the back-end. So why does Laravel choose to use GET for create and edit operations?






laravel







share|improve this question


















  • 2




    The create and edit URLs use GET for showing the forms to create/edit a resource, but saving (changing the records), is handled in the store and update commands, which use POST and PUT/PATCH.
    – Kirk Beard
    Nov 13 at 7:32










  • @KirkBeard So the verbs are specifically for showing what's happening on the UI and not at the back-end?
    – Peter M
    Nov 13 at 7:36








  • 1




    When you load https://example.com/resource/create, that does not change records on on the backed, so it's perfectly acceptable for it to use GET. That page would contain <form method="POST" action="https://example.com/resource/store"> which would process the $_POST data, and modify the records in your database (or wherever they may be).
    – Kirk Beard
    Nov 13 at 7:40
















1














I am picking up on Laravel, and noted that on Laravel's Documentation, it states that the the GET HTTP verb will be handled by the create and edit operations, but from my understanding of REST and CRUD, a create or edit operation actually results in change of records or state on the back-end. So why does Laravel choose to use GET for create and edit operations?






laravel







share|improve this question


















  • 2




    The create and edit URLs use GET for showing the forms to create/edit a resource, but saving (changing the records), is handled in the store and update commands, which use POST and PUT/PATCH.
    – Kirk Beard
    Nov 13 at 7:32










  • @KirkBeard So the verbs are specifically for showing what's happening on the UI and not at the back-end?
    – Peter M
    Nov 13 at 7:36








  • 1




    When you load https://example.com/resource/create, that does not change records on on the backed, so it's perfectly acceptable for it to use GET. That page would contain <form method="POST" action="https://example.com/resource/store"> which would process the $_POST data, and modify the records in your database (or wherever they may be).
    – Kirk Beard
    Nov 13 at 7:40














1












1








1


1





I am picking up on Laravel, and noted that on Laravel's Documentation, it states that the the GET HTTP verb will be handled by the create and edit operations, but from my understanding of REST and CRUD, a create or edit operation actually results in change of records or state on the back-end. So why does Laravel choose to use GET for create and edit operations?






laravel







share|improve this question













I am picking up on Laravel, and noted that on Laravel's Documentation, it states that the the GET HTTP verb will be handled by the create and edit operations, but from my understanding of REST and CRUD, a create or edit operation actually results in change of records or state on the back-end. So why does Laravel choose to use GET for create and edit operations?






laravel




laravel






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 13 at 7:23









Peter M

358315




358315








  • 2




    The create and edit URLs use GET for showing the forms to create/edit a resource, but saving (changing the records), is handled in the store and update commands, which use POST and PUT/PATCH.
    – Kirk Beard
    Nov 13 at 7:32










  • @KirkBeard So the verbs are specifically for showing what's happening on the UI and not at the back-end?
    – Peter M
    Nov 13 at 7:36








  • 1




    When you load https://example.com/resource/create, that does not change records on on the backed, so it's perfectly acceptable for it to use GET. That page would contain <form method="POST" action="https://example.com/resource/store"> which would process the $_POST data, and modify the records in your database (or wherever they may be).
    – Kirk Beard
    Nov 13 at 7:40














  • 2




    The create and edit URLs use GET for showing the forms to create/edit a resource, but saving (changing the records), is handled in the store and update commands, which use POST and PUT/PATCH.
    – Kirk Beard
    Nov 13 at 7:32










  • @KirkBeard So the verbs are specifically for showing what's happening on the UI and not at the back-end?
    – Peter M
    Nov 13 at 7:36








  • 1




    When you load https://example.com/resource/create, that does not change records on on the backed, so it's perfectly acceptable for it to use GET. That page would contain <form method="POST" action="https://example.com/resource/store"> which would process the $_POST data, and modify the records in your database (or wherever they may be).
    – Kirk Beard
    Nov 13 at 7:40








2




2




The create and edit URLs use GET for showing the forms to create/edit a resource, but saving (changing the records), is handled in the store and update commands, which use POST and PUT/PATCH.
– Kirk Beard
Nov 13 at 7:32




The create and edit URLs use GET for showing the forms to create/edit a resource, but saving (changing the records), is handled in the store and update commands, which use POST and PUT/PATCH.
– Kirk Beard
Nov 13 at 7:32












@KirkBeard So the verbs are specifically for showing what's happening on the UI and not at the back-end?
– Peter M
Nov 13 at 7:36






@KirkBeard So the verbs are specifically for showing what's happening on the UI and not at the back-end?
– Peter M
Nov 13 at 7:36






1




1




When you load https://example.com/resource/create, that does not change records on on the backed, so it's perfectly acceptable for it to use GET. That page would contain <form method="POST" action="https://example.com/resource/store"> which would process the $_POST data, and modify the records in your database (or wherever they may be).
– Kirk Beard
Nov 13 at 7:40




When you load https://example.com/resource/create, that does not change records on on the backed, so it's perfectly acceptable for it to use GET. That page would contain <form method="POST" action="https://example.com/resource/store"> which would process the $_POST data, and modify the records in your database (or wherever they may be).
– Kirk Beard
Nov 13 at 7:40












1 Answer
1






active

oldest

votes


















2














As per Laravel creat and edit method uses GET request because they are used to render a view where you can add or update your data. When you submit you form it will use store and update method which are POST and PUT/PATCH request to save the data into database.






share|improve this answer





















    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
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53275822%2fwhy-laravel-resource-create-and-edit-operations-are-depicted-using-get%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    2














    As per Laravel creat and edit method uses GET request because they are used to render a view where you can add or update your data. When you submit you form it will use store and update method which are POST and PUT/PATCH request to save the data into database.






    share|improve this answer


























      2














      As per Laravel creat and edit method uses GET request because they are used to render a view where you can add or update your data. When you submit you form it will use store and update method which are POST and PUT/PATCH request to save the data into database.






      share|improve this answer
























        2












        2








        2






        As per Laravel creat and edit method uses GET request because they are used to render a view where you can add or update your data. When you submit you form it will use store and update method which are POST and PUT/PATCH request to save the data into database.






        share|improve this answer












        As per Laravel creat and edit method uses GET request because they are used to render a view where you can add or update your data. When you submit you form it will use store and update method which are POST and PUT/PATCH request to save the data into database.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 13 at 7:33









        Kamal Paliwal

        730310




        730310






























            draft saved

            draft discarded




















































            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.





            Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


            Please pay close attention to the following guidance:


            • 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.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53275822%2fwhy-laravel-resource-create-and-edit-operations-are-depicted-using-get%23new-answer', 'question_page');
            }
            );

            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







            -

            Popular posts from this blog

            Guess what letter conforming each word

            Image
            6 $begingroup$ This is an entry in the Fortnightly Topic Challenge #41: Short and Sweet. 1 letter only could be mean anything . With an additional letter in front , could be used as medicine component and something you definitely learn or at least heard once. Add another letter in front , you would possibly hear that many times . Add an additional letter in front , you would found an independent country . With an additional letter, in the end , you would found something related to apple . Add another letter in the end , you would found something bad . Hint: Each letter is unique . word knowledge letters chemistry share | improve this question ...
            Read more

            Run scheduled task as local user group (not BUILTIN)

            Image
            0 I am trying to run a scheduled task with User Group (not a single user). This is working fine when I in the field "when running a task, use the following user account:" insert BUILTIN User Group (for example: Administrators or Users). But when I try it with the created Local User Group (example: TestGroup) it is not working. The Users in the TestGroup are the same as in the Administrators group. What could be the problem? Are there some restrictions to the Created User Group compared to BUILTINUsers? scheduled-tasks taskscheduler windowstaskschedule share | improve this question asked Nov 15 '18 at 15:36 Far...
            Read more

            Port of Spain

            Image
            For ports in the country of Spain, see List of ports in Spain. City in City of Port of Spain, Trinidad and Tobago Port of Spain City City of Port of Spain Top to bottom (left to right): Skyline of Port of Spain from Gulf of Paria; National Academy for the Performing Arts, Independence Square, Eric Williams Plaza; MovieTowne, Port of Port of Spain Motto(s):  "We Gather Strength As We Go Along" Port of Spain Coordinates: 10°40′N 61°31′W  /  10.667°N 61.517°W  / 10.667; -61.517 Coordinates: 10°40′N 61°31′W  /  10.667°N 61.517°W  / 10.667; -61.517 Country   Trinidad and Tobago Jurisdiction City of Port of Spain Settled 1560 Incorporated (town) 1853 Incorporated (city) 1914 Government  • Mayor Joel Martinez  • Governing body City Corporation Area [1]  • City 12 km 2 (5 sq mi) Elevation [2] 66 m (217 ft) Population (2011) [1]  • City 37,074  • Rank 3rd  • Density 3,090/km 2 (8,000/sq mi)...
            Read more