v0.0.11 seems to throw a filter error while routing about matador HOT 5 CLOSED

what does your routes.js file look like, and what controller is handling the request, and what does the code look like that handles the beforeFilter.

• Dustin

from matador.

my routes.js

module.exports = { root: [ ['get', '/', 'Home'], ['get', '/about', 'Home', 'about'], ['get', '/registration', 'Registration', 'registration'] ] }

Excerpt from controller (called on index):

    index: function () {
          this.response.render('index', {
                locals: {
                    title: 'Some title'
                }
          })
    },```


beforeFilter is as described in matador's sample

BaseController.js
```, addBeforeFilter: function (actions, fn) {
      if (!fn) { fn = actions, actions = null }
      v(v.is.arr(actions) ? actions : [actions]).each(function (action) {
        beforeFilters.push({
            action: action
          , filter: fn
        })
      })
    }```

```beforeFilters = []```

Wish I could explain to a greater detail, but it's pretty simple, really

Grgur

from matador.

i think i know what happened.... which is likely anyone upgrading to others (i should have bumped this as a minor release, instead of patch).

you'll more than likely need to change the first line of your ApplicationController.js to be this:

module.exports = require('matador').BaseController.extend(function () {

i'm pretty sure i changed over the ownership of the BaseController to be in the module, and not the scaffold

from matador.

You're right, changing it to
module.exports = require('matador').BaseController.extend(function () {})
actually fixed the issue

I updated to 0.0.12, too, and it works just great

Thanks for matador, btw, It's awesome. I have it running in production here: http://sourcedevcon.eu

from matador.

glad that worked! super cool to see it in action :)

from matador.