schmittjoh/JMSSerializerBundle — Issue #49: "PropertyName" Naming Strategy
Author: weaverryan
Created: 2011-11-27 18:56:09+00:00
State: open

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!