Jade template rendering error div despite undefined errors object

Question

When hitting my sign-up page my jade template (with Twitter Bootstrap) is producing an empty error div (i.e. a red, opaque box with a closing link and no errors), despite the errors object returning typeof as 'undefined'. I've used this post for guidance on checking the value of errors. The code follows:

The controller:

/**
 * Show sign up form
 */
exports.signup = function(req, res) {
  res.render('users/signup', {
    title: 'Sign up',
    user: new User()
  });
};

The Jade template:

extends ../layouts/default

block content
  .row
    //-.offset1.span5
    .span6
      a(href="/auth/facebook")
        img(src="/img/icons/facebook.png")
      //- a(href="/auth/github")
        //- img(src="/img/icons/github.png")
      a(href="/auth/twitter")
        img(src="/img/icons/twitter.png")
      a(href="/auth/google")
        img(src="/img/icons/google.png")
    .span6
      if (typeof errors != 'undefined') // The following alert shouldn't be rendered
        .fade.in.alert.alert-block.alert-error
          a.close(data-dismiss="alert", href="javascript:void(0)") x
          ul
            each error in errors
              //- li= error.param
              li= error.msg

      block auth

I've tried the following, but get the same result every time:

if (typeof errors != 'undefined')
if (typeof errors !== 'undefined')
if (typeof errors != undefined)
if (typeof errors !== undefined)
if (null != errors)
if (null !== errors)

Evan · Accepted Answer · 2013-10-28T01:26:19.520

0

EDIT: From what you said in the comments, errors is not undefined when there are no errors; instead, it is an empty array. This answer now checks for that instead.

It would help to see this working somewhere, but it's possible that changing your Jade code to this will solve it:

  - if (errors.length > 0) {// The following alert shouldn't be rendered
    .fade.in.alert.alert-block.alert-error
      a.close(data-dismiss="alert", href="javascript:void(0)") x
      ul
        each error in errors
          //- li= error.param
          li= error.msg
  - }

edited Oct 28 '13 at 01:26

answered Oct 28 '13 at 01:15

Evan

825
4
14

Thanks, @Evan, but no dice. Wrapping the block in -s and {}s produces the same result. – CrankNPlank Oct 28 '13 at 01:19
Have you dropped a `- console.log( errors )` in there to see what Jade thinks errors is at that exact moment? – Evan Oct 28 '13 at 01:21
Yeah, and all that are returned are empty brackets []. – CrankNPlank Oct 28 '13 at 01:24
Okay. I'm changing this answer to detect that! – Evan Oct 28 '13 at 01:25
You're the man, @Evan. That did it. I feel stupid for not catching that. Thanks! – CrankNPlank Oct 28 '13 at 01:29
It happens to us all! – Evan Oct 28 '13 at 01:30

Jade template rendering error div despite undefined errors object

1 Answers1