"PropertyName" Naming Strategy

[weaverryan]

Hi guys!

I was wondering if there was a specific reason for not having a naming strategy that simply uses the property name as the end field name. The use case is serializing an object for consumption by a BackboneJS model, but then a server-side Sf2 form to handle the BackboneJS model save (e.g. deserialize the posted data then proxy through a form).

Unless anyone can see a reason against this, I'm happy to make a PR for this.

Thanks!

[schmittjoh]

Sounds good to me.

On Sun, Nov 27, 2011 at 7:56 PM, Ryan Weaver <
reply@reply.github.com

wrote:

Hi guys!

I was wondering if there was a specific reason for not having a naming
strategy that simply uses the property name as the end field name. The use
case is serializing an object for consumption by a BackboneJS model, but
then a server-side Sf2 form to handle the BackboneJS model save (e.g.
deserialize the posted data then proxy through a form).

Unless anyone can see a reason against this, I'm happy to make a PR for
this.

Thanks!

---

Reply to this email directly or view it on GitHub:
#49

[lsmith77]

+1

[jgornick]

👍

[srosato]

+1

[ianunruh]

+1

[wheelsandcogs]

This would remove the need for #139 for me (although there's no reason both shouldn't be available).

[ruimarinho]

+1 this would be really nice!

[marco-santamaria]

+1

[madhatter42]

@weaverryan just wondering if you've been able to make any progress on this (or are planning to)?

[fredjiles]

+1

[schmittjoh]

This is super simple to implement. If you really need it, please someone send a PR instead of adding +1s on this issue.