How can I organize laravel routes without repeating controller and functions?












-1















I have this code, but it's very verbose. How Can I write that shorter?



Route::get('/transaction/index', 'TransacaoController@index');
Route::get('/transaction/test1', 'TransacaoController@test1');
Route::get('/transaction/test2', 'TransacaoController@test2');
Route::get('/transaction/test3', 'TransacaoController@test3');
Route::get('/transaction/test4', 'TransacaoController@test4');









share|improve this question


















  • 1





    Can you add more explanation? Like what will each one of your routes do? And what the result should look like?

    – nomorehere
    Nov 15 '18 at 22:30


















-1















I have this code, but it's very verbose. How Can I write that shorter?



Route::get('/transaction/index', 'TransacaoController@index');
Route::get('/transaction/test1', 'TransacaoController@test1');
Route::get('/transaction/test2', 'TransacaoController@test2');
Route::get('/transaction/test3', 'TransacaoController@test3');
Route::get('/transaction/test4', 'TransacaoController@test4');









share|improve this question


















  • 1





    Can you add more explanation? Like what will each one of your routes do? And what the result should look like?

    – nomorehere
    Nov 15 '18 at 22:30
















-1












-1








-1








I have this code, but it's very verbose. How Can I write that shorter?



Route::get('/transaction/index', 'TransacaoController@index');
Route::get('/transaction/test1', 'TransacaoController@test1');
Route::get('/transaction/test2', 'TransacaoController@test2');
Route::get('/transaction/test3', 'TransacaoController@test3');
Route::get('/transaction/test4', 'TransacaoController@test4');









share|improve this question














I have this code, but it's very verbose. How Can I write that shorter?



Route::get('/transaction/index', 'TransacaoController@index');
Route::get('/transaction/test1', 'TransacaoController@test1');
Route::get('/transaction/test2', 'TransacaoController@test2');
Route::get('/transaction/test3', 'TransacaoController@test3');
Route::get('/transaction/test4', 'TransacaoController@test4');






php laravel web controller routes






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 15 '18 at 22:14









Lucas GustavoLucas Gustavo

1




1








  • 1





    Can you add more explanation? Like what will each one of your routes do? And what the result should look like?

    – nomorehere
    Nov 15 '18 at 22:30
















  • 1





    Can you add more explanation? Like what will each one of your routes do? And what the result should look like?

    – nomorehere
    Nov 15 '18 at 22:30










1




1





Can you add more explanation? Like what will each one of your routes do? And what the result should look like?

– nomorehere
Nov 15 '18 at 22:30







Can you add more explanation? Like what will each one of your routes do? And what the result should look like?

– nomorehere
Nov 15 '18 at 22:30














2 Answers
2






active

oldest

votes


















1














Not sure if you're talking about the Route Prefixes in Laravel.



Route Prefixes
The prefix method may be used to prefix each route in the group with a given URI. For example, you may want to prefix all route URIs within the group with admin:



Route::prefix('admin')->group(function () {
Route::get('users', function () {
// Matches The "/admin/users" URL
});
});


Extracted from https://laravel.com/docs/5.7/routing






share|improve this answer































    1














    It might depends on how you prefer organize your infrastructure. Writing less not always is synonym of order.



    You can use group() to apply middleware or prefixes to your routes:



    Route::group(['middleware' => ['custom'], 'prefix' => 'transaction'], function(){
    Route::get('/index', 'TransacaoController@index');
    Route::get('/test1', 'TransacaoController@test1');
    Route::get('/test2', 'TransacaoController@test2');
    Route::get('/test3', 'TransacaoController@test3');
    Route::get('/test4', 'TransacaoController@test4');
    });


    Now, there is another option (does not recommended). You can use a unique route making the separation of your logic at controller level:



    Route::get('/transaction/{action}', 'TransacaoController@action');

    function action($action){
    if ($action == 'index'){
    // ...
    }
    }





    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%2f53328640%2fhow-can-i-organize-laravel-routes-without-repeating-controller-and-functions%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









      1














      Not sure if you're talking about the Route Prefixes in Laravel.



      Route Prefixes
      The prefix method may be used to prefix each route in the group with a given URI. For example, you may want to prefix all route URIs within the group with admin:



      Route::prefix('admin')->group(function () {
      Route::get('users', function () {
      // Matches The "/admin/users" URL
      });
      });


      Extracted from https://laravel.com/docs/5.7/routing






      share|improve this answer




























        1














        Not sure if you're talking about the Route Prefixes in Laravel.



        Route Prefixes
        The prefix method may be used to prefix each route in the group with a given URI. For example, you may want to prefix all route URIs within the group with admin:



        Route::prefix('admin')->group(function () {
        Route::get('users', function () {
        // Matches The "/admin/users" URL
        });
        });


        Extracted from https://laravel.com/docs/5.7/routing






        share|improve this answer


























          1












          1








          1







          Not sure if you're talking about the Route Prefixes in Laravel.



          Route Prefixes
          The prefix method may be used to prefix each route in the group with a given URI. For example, you may want to prefix all route URIs within the group with admin:



          Route::prefix('admin')->group(function () {
          Route::get('users', function () {
          // Matches The "/admin/users" URL
          });
          });


          Extracted from https://laravel.com/docs/5.7/routing






          share|improve this answer













          Not sure if you're talking about the Route Prefixes in Laravel.



          Route Prefixes
          The prefix method may be used to prefix each route in the group with a given URI. For example, you may want to prefix all route URIs within the group with admin:



          Route::prefix('admin')->group(function () {
          Route::get('users', function () {
          // Matches The "/admin/users" URL
          });
          });


          Extracted from https://laravel.com/docs/5.7/routing







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Nov 15 '18 at 22:26









          Code MajicCode Majic

          10510




          10510

























              1














              It might depends on how you prefer organize your infrastructure. Writing less not always is synonym of order.



              You can use group() to apply middleware or prefixes to your routes:



              Route::group(['middleware' => ['custom'], 'prefix' => 'transaction'], function(){
              Route::get('/index', 'TransacaoController@index');
              Route::get('/test1', 'TransacaoController@test1');
              Route::get('/test2', 'TransacaoController@test2');
              Route::get('/test3', 'TransacaoController@test3');
              Route::get('/test4', 'TransacaoController@test4');
              });


              Now, there is another option (does not recommended). You can use a unique route making the separation of your logic at controller level:



              Route::get('/transaction/{action}', 'TransacaoController@action');

              function action($action){
              if ($action == 'index'){
              // ...
              }
              }





              share|improve this answer




























                1














                It might depends on how you prefer organize your infrastructure. Writing less not always is synonym of order.



                You can use group() to apply middleware or prefixes to your routes:



                Route::group(['middleware' => ['custom'], 'prefix' => 'transaction'], function(){
                Route::get('/index', 'TransacaoController@index');
                Route::get('/test1', 'TransacaoController@test1');
                Route::get('/test2', 'TransacaoController@test2');
                Route::get('/test3', 'TransacaoController@test3');
                Route::get('/test4', 'TransacaoController@test4');
                });


                Now, there is another option (does not recommended). You can use a unique route making the separation of your logic at controller level:



                Route::get('/transaction/{action}', 'TransacaoController@action');

                function action($action){
                if ($action == 'index'){
                // ...
                }
                }





                share|improve this answer


























                  1












                  1








                  1







                  It might depends on how you prefer organize your infrastructure. Writing less not always is synonym of order.



                  You can use group() to apply middleware or prefixes to your routes:



                  Route::group(['middleware' => ['custom'], 'prefix' => 'transaction'], function(){
                  Route::get('/index', 'TransacaoController@index');
                  Route::get('/test1', 'TransacaoController@test1');
                  Route::get('/test2', 'TransacaoController@test2');
                  Route::get('/test3', 'TransacaoController@test3');
                  Route::get('/test4', 'TransacaoController@test4');
                  });


                  Now, there is another option (does not recommended). You can use a unique route making the separation of your logic at controller level:



                  Route::get('/transaction/{action}', 'TransacaoController@action');

                  function action($action){
                  if ($action == 'index'){
                  // ...
                  }
                  }





                  share|improve this answer













                  It might depends on how you prefer organize your infrastructure. Writing less not always is synonym of order.



                  You can use group() to apply middleware or prefixes to your routes:



                  Route::group(['middleware' => ['custom'], 'prefix' => 'transaction'], function(){
                  Route::get('/index', 'TransacaoController@index');
                  Route::get('/test1', 'TransacaoController@test1');
                  Route::get('/test2', 'TransacaoController@test2');
                  Route::get('/test3', 'TransacaoController@test3');
                  Route::get('/test4', 'TransacaoController@test4');
                  });


                  Now, there is another option (does not recommended). You can use a unique route making the separation of your logic at controller level:



                  Route::get('/transaction/{action}', 'TransacaoController@action');

                  function action($action){
                  if ($action == 'index'){
                  // ...
                  }
                  }






                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Nov 15 '18 at 22:29









                  manixmanix

                  10.2k85185




                  10.2k85185






























                      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.




                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function () {
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53328640%2fhow-can-i-organize-laravel-routes-without-repeating-controller-and-functions%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

                      鏡平學校

                      ꓛꓣだゔៀៅຸ໢ທຮ໕໒ ,ໂ'໥໓າ໼ឨឲ៵៭ៈゎゔit''䖳𥁄卿' ☨₤₨こゎもょの;ꜹꟚꞖꞵꟅꞛေၦေɯ,ɨɡ𛃵𛁹ޝ޳ޠ޾,ޤޒޯ޾𫝒𫠁သ𛅤チョ'サノބޘދ𛁐ᶿᶇᶀᶋᶠ㨑㽹⻮ꧬ꧹؍۩وَؠ㇕㇃㇪ ㇦㇋㇋ṜẰᵡᴠ 軌ᵕ搜۳ٰޗޮ޷ސޯ𫖾𫅀ल, ꙭ꙰ꚅꙁꚊꞻꝔ꟠Ꝭㄤﺟޱސꧨꧼ꧴ꧯꧽ꧲ꧯ'⽹⽭⾁⿞⼳⽋២៩ញណើꩯꩤ꩸ꩮᶻᶺᶧᶂ𫳲𫪭𬸄𫵰𬖩𬫣𬊉ၲ𛅬㕦䬺𫝌𫝼,,𫟖𫞽ហៅ஫㆔ాఆఅꙒꚞꙍ,Ꙟ꙱エ ,ポテ,フࢰࢯ𫟠𫞶 𫝤𫟠ﺕﹱﻜﻣ𪵕𪭸𪻆𪾩𫔷ġ,ŧآꞪ꟥,ꞔꝻ♚☹⛵𛀌ꬷꭞȄƁƪƬșƦǙǗdžƝǯǧⱦⱰꓕꓢႋ神 ဴ၀க௭எ௫ឫោ ' េㇷㇴㇼ神ㇸㇲㇽㇴㇼㇻㇸ'ㇸㇿㇸㇹㇰㆣꓚꓤ₡₧ ㄨㄟ㄂ㄖㄎ໗ツڒذ₶।ऩछएोञयूटक़कयँृी,冬'𛅢𛅥ㇱㇵㇶ𥄥𦒽𠣧𠊓𧢖𥞘𩔋цѰㄠſtʯʭɿʆʗʍʩɷɛ,əʏダヵㄐㄘR{gỚṖḺờṠṫảḙḭᴮᵏᴘᵀᵷᵕᴜᴏᵾq﮲ﲿﴽﭙ軌ﰬﶚﶧ﫲Ҝжюїкӈㇴffצּ﬘﭅﬈軌'ffistfflſtffतभफɳɰʊɲʎ𛁱𛁖𛁮𛀉 𛂯𛀞నఋŀŲ 𫟲𫠖𫞺ຆຆ ໹້໕໗ๆทԊꧢꧠ꧰ꓱ⿝⼑ŎḬẃẖỐẅ ,ờỰỈỗﮊDžȩꭏꭎꬻ꭮ꬿꭖꭥꭅ㇭神 ⾈ꓵꓑ⺄㄄ㄪㄙㄅㄇstA۵䞽ॶ𫞑𫝄㇉㇇゜軌𩜛𩳠Jﻺ‚Üမ႕ႌႊၐၸဓၞၞၡ៸wyvtᶎᶪᶹစဎ꣡꣰꣢꣤ٗ؋لㇳㇾㇻㇱ㆐㆔,,㆟Ⱶヤマފ޼ޝަݿݞݠݷݐ',ݘ,ݪݙݵ𬝉𬜁𫝨𫞘くせぉて¼óû×ó£…𛅑הㄙくԗԀ5606神45,神796'𪤻𫞧ꓐ㄁ㄘɥɺꓵꓲ3''7034׉ⱦⱠˆ“𫝋ȍ,ꩲ軌꩷ꩶꩧꩫఞ۔فڱێظペサ神ナᴦᵑ47 9238їﻂ䐊䔉㠸﬎ffiﬣ,לּᴷᴦᵛᵽ,ᴨᵤ ᵸᵥᴗᵈꚏꚉꚟ⻆rtǟƴ𬎎

                      Why https connections are so slow when debugging (stepping over) in Java?