1602 / 1602/compound

Router matching multiple routes to controllers

Abierto
#640 1 comentario 0 reacciones 0 asignados Ver en GitHub
Lenguaje dominante
JavaScript
Estrellas
1.6k
Forks
179
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

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.

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Stack tecnológico
javascript, node.js
Área
api, backend
Tipo de issue
Error
Dificultad
3/5
Tiempo estimado
1-2 días
Estado de actividad
Estancado
Claridad
Bien especificado
Aptitud para principiantes
55/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.