Iterate through properties of current context objects in Dust.js

Question

Given the JSON object:

errors =
{ 
  hashed_password: { 
     message: 'Validator "Password cannot be blank" failed for path hashed_password',
     name: 'ValidatorError',
     path: 'hashed_password',
     type: 'Password cannot be blank' },
  username: { 
     message: 'Validator "Username cannot be blank" failed for path username',
     name: 'ValidatorError',
     path: 'username',
     type: 'Username cannot be blank' },
  email: {
     message: 'Validator "Email cannot be blank" failed for path email',
     name: 'ValidatorError',
     path: 'email',
     type: 'Email cannot be blank' },
  name: { 
     message: 'Validator "Name cannot be blank" failed for path name',
     name: 'ValidatorError',
     path: 'name',
     type: 'Name cannot be blank' } 
}

How do I iterate through the properties of each "current context" object?

I would think you do something like this:

{#errors}
    {#.}
         {type}
    {/.}
{/errors}

Root issue: in what order would you want your output to be in? — spectras
– spectras, Commented Mar 2, 2015 at 16:47

Community · Accepted Answer · 2017-05-23 12:06:27Z

4

If you really have to put meaningful data into object keys, consider writing a contextual helper, as per:

edited May 23, 2017 at 12:06

CommunityBot

11 silver badge

answered Mar 8, 2013 at 11:59

Alex T

1558 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

smfoote · Accepted Answer · 2013-03-06 16:48:36Z

0

It is not possible to iterate through members of an object in Dust. Part of the reason is that you cannot know the order of the members. Another part is that this is seen as bringing too much logic into Dust.

Instead, you can change the JSON to look more like this:

{
  errors: [
    {
      hashed_password: { 
        message: 'Validator "Password cannot be blank" failed for path hashed_password',
        name: 'ValidatorError',
        path: 'hashed_password',
        type: 'Password cannot be blank'
      }
    },
    {
      username: { 
        message: 'Validator "Username cannot be blank" failed for path username',
        name: 'ValidatorError',
        path: 'username',
        type: 'Username cannot be blank'
      }
    },
    {
      email: {
        message: 'Validator "Email cannot be blank" failed for path email',
        name: 'ValidatorError',
        path: 'email',
        type: 'Email cannot be blank'
      }
    },
    {
      name: { 
        message: 'Validator "Name cannot be blank" failed for path name',
        name: 'ValidatorError',
        path: 'name',
        type: 'Name cannot be blank'
    }
  ]
}

edited Mar 6, 2013 at 16:48

answered Mar 6, 2013 at 5:59

smfoote

5,6695 gold badges35 silver badges38 bronze badges

1 Comment

Dan Kanze Over a year ago

So could you site a snippet of the most efficient way of doing what I'm trying to do?

user457586 · Accepted Answer · 2015-02-04 17:23:46Z

0

You can iterate over an object using a helper.

For example, you could define a helper like this one:

dust.helpers.iter = function(chunk, context, bodies, params) {
  var obj = dust.helpers.tap(params.obj, chunk, context);

  var iterable = [];

  for (var key in obj) {
    if (obj.hasOwnProperty(key)) {
      var value = obj[key];

      iterable.push({
        '$key': key,
        '$value': value,
        '$type': typeof value
      });
    }
  }

  return chunk.section(iterable, context, bodies);
};

Then, in your template, you would loop through like this:

{@iter obj=errors}
  {$value.type}
{/iter}

answered Feb 4, 2015 at 17:23

user457586

1 Comment

spectras Over a year ago

Although that technically works, keep in mind that the order the elements will be rendered in is not defined, and might even change every time you render the template. You might want to build the list of keys into an array, sort it and only then iterate on that.

Collectives™ on Stack Overflow

Iterate through properties of current context objects in Dust.js

3 Answers 3

Comments

1 Comment

1 Comment

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

Comments

1 Comment

1 Comment

Your Answer

Sign up or log in

Post as a guest

Linked

Related