No one should ever have to keep writing app.use( /someRoute , require( someFile )) until it forms a heap of code.

Question

因此,Im开始使用Node.js。我在上看到了与Ryan Dahl的录像,并听到他建议为网站提供快车。

我下载了最新版本的快递,并开始编码。我对......有完全成熟的静态看法,但一旦我尝试派遣参数,我就会发现这样的错误:

Cannot GET /wiki

我在“上尝试过,但最新版本中一个使用路线的改变使指南无法使用。

指南:

app.get( /users/:id? , function(req, res, next){
    var id = req.params.id;
    if (id) {
        // do something
    } else {
        next();
    }
});

Generated by Express:

app.get( / , routes.index);

My problem arises when I try and add another route.

app.get( /wiki , routes.wiki_show);

我尝试了一套办法,但我保留了<代码>。 Cannot GET /wiki (404) 差错。

routes/index.js looks like this:

exports.index = function(req, res) {
    res.render( index , { title:  Test , articles: articles, current_article: current_article, sections: sections })
};

The only thing I did there was add some parameters (arrays in the same file) and this i working. But when I copy the contents and change exports.index to exports.wiki or exports.wiki_show I still get the Cannot GET /wiki error.

Can anyone explain to me what I m missing here? - Thanks.

Answer 1

So, after I created my question, I got this related list on the right with a similar issue: Organize routes in Node.js.

该职位的答案与,建议查看 route-separation 。例如。

这有助于我改变我的法典,我现在就这样做了。感谢您的评论。

我的实施工作最终就是这样;

我需要的是我的路线:

var express = require( express )
  , site = require( ./site )
  , wiki = require( ./wiki );

此外,我还要说:

app.get( / , site.index);
app.get( /wiki/:id , wiki.show);
app.get( /wiki/:id/edit , wiki.edit);

我有两处档案,称为维基。 j 根植于我,包括:

exports.edit = function(req, res) {

    var wiki_entry = req.params.id;

    res.render( wiki/edit , {
        title:  Editing Wiki ,
        wiki: wiki_entry
    })
}

Answer 2

举例来说,ur路与 objects相匹配,而后者则与http verbs与功能相匹配。这在树中铺设了一条路,简明易读。这些信标实体也作为随附方法具有功能的物体书写。

var express = require( ../../lib/express )
  , verbose = process.env.NODE_ENV !=  test 
  , app = module.exports = express();

app.map = function(a, route){
  route = route ||   ;
  for (var key in a) {
    switch (typeof a[key]) {
      // {  /path : { ... }}
      case  object :
        app.map(a[key], route + key);
        break;
      // get: function(){ ... }
      case  function :
        if (verbose) console.log( %s %s , key, route);
        app[key](route, a[key]);
        break;
    }
  }
};

var users = {
  list: function(req, res){
    res.send( user list );
  },

  get: function(req, res){
    res.send( user   + req.params.uid);
  },

  del: function(req, res){
    res.send( delete users );
  }
};

var pets = {
  list: function(req, res){
    res.send( user   + req.params.uid +   s pets );
  },

  del: function(req, res){
    res.send( delete   + req.params.uid +   s pet   + req.params.pid);
  }
};

app.map({
   /users : {
    get: users.list,
    del: users.del,
     /:uid : {
      get: users.get,
       /pets : {
        get: pets.list,
         /:pid : {
          del: pets.del
        }
      }
    }
  }
});

app.listen(3000);

Answer 3

Seems that only index.js get loaded when you require("./routes") . I used the following code in index.js to load the rest of the routes:

var fs = require( fs )
  , path = require( path );

fs.readdirSync(__dirname).forEach(function(file){
  var route_fname = __dirname +  /  + file;
  var route_name = path.basename(route_fname,  .js );
  if(route_name !==  index  && route_name[0] !== "."){ 
    exports[route_name] = require(route_fname)[route_name];
  }
});

Answer 4

你们也可以将其组织成单元。因此,这是一样的。

./
controllers
    index.js
    indexController.js
app.js

之后,控制器的管理人在索引库内出口控制器。

//indexController.js
module.exports = function(){
//do some set up

var self = {
     indexAction : function (req,res){
       //do your thing
}
return self;
};

然后是指数。

exports.indexController = require("./indexController");

最后,见附录一。

var controllers = require("./controllers");

app.get("/",controllers.indexController().indexAction);

I think this approach allows for clearer seperation and also you can configure your controllers by passing perhaps a db connection in.

Answer 5

No one should ever have to keep writing app.use( /someRoute , require( someFile )) until it forms a heap of code.

援引/确定路线的花费时间是毫无意义的。即便你确实需要海关控制,但有时可能只是一些时候,而且对于你想要能够建立标准档案结构,并自动拥有一个模块。

Try Route Magic

在您的表态中,轮任会开始形成一种无用的庞大的法规。你们只想用两条法典处理所有<代码>应用程序。

const magic = require( express-routemagic )
magic.use(app, __dirname,  [your route directory] )

For those you want to handle manually, just don t use pass the directory to Magic.

No one should ever have to keep writing app.use( /someRoute , require( someFile )) until it forms a heap of code.

友情链接