Node.js Express 路由命名和排序:优先级如何确定? [英] Node.js Express route naming and ordering: how is precedence determined?
问题描述
假设我的 Express 应用程序中有一些 GET 路由:
Say I've got a few GET routes on my Express application:
// music albums
app.get('/api/albums', routes.albums.getAlbums);
app.get('/api/albums/:id', routes.albums.getAlbum);
app.get('/api/albums/artwork', routes.albums.getAlbumArtwork);
我尝试使用以下 jQuery AJAX 片段来攻击它们:
and I attempt to hit them using the follow jQuery AJAX snippet:
$("#retrieveAlbumArtwork").on("click", function() {
$.ajax({
url: "api/albums/artwork",
type: "GET",
data: {
artist: $("#albumArtist").val(),
title: $("#albumTitle").val()
},
// ... callbacks and such
由于某种原因,此调用使用 /:id
参数而不是显式的 /artwork
路由命中第二个处理程序.像这样交换它们会使它们按预期运行:
For some reason, this call hits the second handler, with the /:id
parameter, instead of the explicit /artwork
route. Swapping them like so makes them function as expected:
// music albums
app.get('/api/albums', routes.albums.getAlbums);
app.get('/api/albums/artwork', routes.albums.getAlbumArtwork);
app.get('/api/albums/:id', routes.albums.getAlbum);
有人能准确解释为什么会这样吗?我假设 Express 足够聪明,可以识别 id 参数 (/albums/23453243
) 与查询字符串 (/albums/artwork?artist=artistName&title=albumTitle
)并适当地路由,但似乎不是这样?
Can someone explain exactly why this is happening? I would assume Express would be smart enough to identify an id param (/albums/23453243
) versus a querystring (/albums/artwork?artist=artistName&title=albumTitle
) and route appropriately, but this doesn't seem to be the case?
推荐答案
不,不是.:id
将匹配任何内容.所以 /api/albums/artwork
对于该匹配是完全有效的.Express 也支持 RegExp 匹配.因此,您可以使用 RegExp 进行显式数字匹配路由.
No it isn't. :id
will match anything. So /api/albums/artwork
is totally valid for that match. Express does support RegExp match also. So you could make an explicit numeric matching route using RegExp.
另一种选择是使用 app.param
,如 API 文档中所述:https://expressjs.com/en/api.html#app.param
Another option is using app.param
as explained in the API documentation here: https://expressjs.com/en/api.html#app.param
这允许你为路由器定义匹配的参数,这样你就可以有一个像 /api/albums/:albumId
这样的 URL,其中 :albumId
必须是数字,你如果您愿意,也可以在此时验证 albumId
.
This allows you to define matching params for the router so you could have a URL like /api/albums/:albumId
where :albumId
has to be numeric, you could also validate an albumId
at this point if you wished too.
但总的来说,第二种方式你做的很正常,通常我把静态路由放在顶部,然后是动态路由,然后是全部捕获,然后是错误处理程序.
But in all, the second way you are doing it fairly normal, generally I put static routes at the top, then dynamic routes, catch all, then error handlers.
这篇关于Node.js Express 路由命名和排序:优先级如何确定?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!