Multi-dimentional Collection field values not showing up

[marcelosalloum]

Hi folks,

I've a problem when my models are multi-dimensional. What I mean is, when my user model look like this:

// Single-dimensional scheme
var userSchema1 = mongoose.Schema({
  email    : String,
  password : String,
};

node-penguin works perfectly fine, but when my models look like:

// Multi-dimensional scheme
var userSchema2 = mongoose.Schema({
  local    : {
    email    : String,
    password : String,
  }
};

the admin fields show up empty. The field names show up like "local.email" and "local.password", which is perfectly fine, but the values are empty.

I am not sure on how to fix that but if anyone could give me some guideline, I can definitely give it a shot and even make a pull request if I get successful.

Thanks,

[aularon]

Hello Marcelo,

This case (nested objects) is not addressed yet in the current version. Handling it will probably require some changes in the form.jade on how to render the form (nested[arrays] maybe?), and then handling the submitted POST in src/index.coffee#rEdit in a recursive manner.

The document at https://github.com/etabits/node-penguin/blob/master/doc/layers.md outlines how the request is sent from the user, through different layers, until finally saved in the db.

I will be working on this issue whenever I get the time to, it is a high priority. Any pull request addressing it is, as always, most welcome :-)

Thanks!

[marcelosalloum]

Thanks @aularon.

I've found out that the issue is happening in file src/index.coffee@rEditEmpty:353 , where you do:

req.$p.renderObj.form = req.$p.form.bind(req.$p.row)

I seems to be an issue with the "forms" lib. For the case of nested objects, the value and data fields are showing as "undefined" and "", instead of the actual values.

Not sure how to edit that bind function. Do you have any suggestion?

[aularon]

I would transform the req.$p.row structure to one that is understood by the form .bind method, so it will successfully load the fields values from the POST request. It needs to be done either by restructuring the field names in the form html itself (form.jade), and/or by doing some magic before calling .bind.

[marcelosalloum]

Actually, when it comes to the form.jade file, the "form.fields" dict has already lost the nested objects value. So I believe the only option would be doing some magic before calling .bind, although I could not manage to do so, as the row has a lot of information and my workaround did not work at all.

Wish you have better luck (and skills) when it comes to your turn.

Thanks,

[sogko]

Hi guys,

I had similar needs for my own project and added support for nested fields / multidimensional fields to penguin as pull request #9

I've updated the examples folder as well to show how it would work.

@marcelosalloum Let me know if this does or does not cover your use-case. I'd be happy to help out.

Some screenshots of the example project

Here's how the User collection was seeded in the example

var User = [
  {
    _id: IDs[0],
    username: 'Master',
    email: 'master@example.org',
    password: 'plaintextpass',
    isAdmin: true,
    data: {
      alternateEmail: 'master2@example.org'
    },
    meta: {
      slug: 'admin-master',
      settings: {
        hasLoggedOn: false,
        lastLoginDate: Date.now()
      },
      deepMeta: {
        deepSlug: 'deep-admin-master'
      }
    },
    tags: ['admin', 'master', 'keyMaster']
  },
  {
    _id: IDs[1],
    username: 'Peon',
    email: 'peon@example.org',
    password: 'usebcrypttostorepasswords!',
    isAdmin: false
  }
];