1602 / 1602/compound

Router matching multiple routes to controllers

Aperta
#640 1 commento 0 reazioni 0 assegnatari Vedi su GitHub
Lingua principale
JavaScript
Stelle
1.6k
Fork
179
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Descrizione

I have the following routes defined:

``` javascript
exports.routes = function (map) {
map.all('admin/:controller/:action');
map.all('admin/:controller/:action/:id');
map.all(':controller/:action');
map.all(':controller/:action/:id');
};
```

When I visit /admin/mycontroller/index, I see in my console that compound is trying to access both:

```
Params: {"controller":"mycontroller","action":"index"} // this is correct
Params: {"controller":"admin","action":"mycontroller","id":"index"}
```

But I was expecting only the first to be routed. Is this a bug? Yes, both routes are valid, but only one is supposed to be executed, not every matching route.

Guida per i contributori

Nessuna guida per i contributori indicizzata per questo repository

Direzione di ricerca

Look at the router implementation in the compound framework, likely in a file like lib/router.js. The issue shows that multiple route patterns are being matched when only one should be. Start by understanding how the map.all method works and how route precedence is determined. Test by creating a simple app with the given routes and logging the matching logic to see why both are triggered.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Valutazione

Stack tecnologico
javascript, node.js
Ambito
api, backend
Tipo di issue
Bug
Difficoltà
3/5
Tempo stimato
1-2 giorni
Stato di attività
Ferma
Chiarezza
Specificata chiaramente
Idoneità per principianti
55/100

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.