Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

Middlewares not being called when using wildcard "*"

未关闭
  • 哪里不对？
#112 4 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
35/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
停滞
技术栈
aws, javascript, node.js
领域
api, backend

调研方向

从 api.use 中间件注册和通配符路径处理入手，使用列出的 /data/* authorize 中间件进行复现。验证存在此注册时中间件顺序和路径匹配的行为；完成的标准是通用中间件仍然运行，并且 authorize 仍限定在 /data/* 范围内。

由索引模型根据 Issue 内容生成。

描述

Lambda api: 0.10.1

I have this API:

const api = require('lambda-api')({base: 'v2'})
  , middleware = require('../utils/middleware')
  , LiveblogApi = require('../apis/liveblogApi');

//apply middlewares
api.use(middleware.addCorsHeaders);
api.use(middleware.logRequest);
api.use(['/data/*'], middleware.authorize);
api.use(middleware.populateCommonHeaders);
api.use(middleware.errorHandler);

api.post('/data/pbp/:eventId', async (req, res) => {
  let response = await LiveblogApi.addPost(req.params.eventId, req.body);
  return res.json(response);
});

api.post('/data/pbp/:eventId/:key', async (req, res) => {
  let response = await LiveblogApi.setPost(req.params.eventId, req.params.key, req.body);
  return res.json(response);
});

api.delete('/data/pbp/:eventId/:key', async (req, res) => {
  let response = await LiveblogApi.deletePost(req.params.eventId, req.params.key);
  return res.json(response);
});

api.post('/data/drafts/:eventId', async (req, res) => {
  let response = await LiveblogApi.addDraft(req.params.eventId, req.body);
  return res.json(response);
});

api.post('/data/drafts/:eventId/:key', async (req, res) => {
  let response = await LiveblogApi.setDraft(req.params.eventId, req.params.key, req.body);
  return res.json(response);
});

api.delete('/data/drafts/:eventId/:key', async (req, res) => {
  let response = await LiveblogApi.deleteDraft(req.params.eventId, req.params.key);
  return res.json(response);
});

api.delete('/data/comments/:eventId/:postId/:key', async (req, res) => {
  let response = await LiveblogApi.deleteComment(req.params.eventId, req.params.postId, req.params.key);
  return res.json(response);
});

module.exports = api;

You can see that I have another JS module that holds all middlewares. When I deploy it like this, it looks like only the authorize middleware is being called.

If I remove the line:
api.use(['/data/*'], middleware.authorize);

Then the other middlewares are called normally.

In old versions of the lib this didn't happen, I just updated to the newest version and deployed again.

My workaround:
api.use(middleware.authorize); which has the same effect as before.

主要语言
JavaScript
星标
1.5k
派生
127
30 天内没有已合并 PR

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

jeremydaly/lambda-api 的其他 Issue

查看 jeremydaly/lambda-api 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。