How can I organize laravel routes without repeating controller and functions?
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
add a comment |
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
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
add a comment |
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
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
php laravel web controller routes
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
add a comment |
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
add a comment |
2 Answers
2
active
oldest
votes
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
add a comment |
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'){
// ...
}
}
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%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
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
add a comment |
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
add a comment |
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
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
answered Nov 15 '18 at 22:26
Code MajicCode Majic
10510
10510
add a comment |
add a comment |
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'){
// ...
}
}
add a comment |
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'){
// ...
}
}
add a comment |
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'){
// ...
}
}
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'){
// ...
}
}
answered Nov 15 '18 at 22:29
manixmanix
10.2k85185
10.2k85185
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%2f53328640%2fhow-can-i-organize-laravel-routes-without-repeating-controller-and-functions%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
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