req.options.controller not set, camelCase serialization not working

[danieledraganti]

Hello,
I am using your blueprint system on an app with Ember.js as a front end, which is of course the ideal platform for JSON API 😊
I am running on Sails 1.0.0-36.
I am calling the JsonApiService inside of a controller to handle user signup.
This is a stub of the code I have made to check if the JSON API integration works:

signup: function (req, res) {
	  req.options.controller = 'user';
	  JsonApiService.createRecord(req, res);
  }

I would like to point out two bugs:

1. I need to manually set req.options.controller since this is used by your parseModel to retrieve the actual model of the resource, but Sails does not set this value automatically.
2. I am receiving the parameters as 'kebab-case' from my front end, therefore your service should serialize them correctly when injected in the Sails model, to camelCase (I have set attributesDeserializedCase: 'camelCase'in the config/jsonapi.js), but Waterline triggers the following error:

UsageError: Invalid new record(s).
Details:
  Could not use specified `first-name`.  This is not a valid name for an attribute.

Where does your code do the serializing/deserializing? What is happening here?

Thank you in advance.

[GoldenChrysus]

It's easier to resolve this if you handle it through Ember. In your API serializer file (/app/serializers/application.js), you can add:

keyForRelationship(key) { 
	return key;
},
keyForAttribute(key) {
	return key;
}

Then you will set up your models in Ember and Sails to have the same casing, which will resolve any attribute/relationship casing communication errors between the two systems.

[dynamiccast]

@danidr Sorry I have been away for this long. Github do not notify me and I do not work with Sails anymore. Do you still have an issue with this module ?

[danieledraganti]

Hello, sorry but I haven't tried to implement it back on my custom method (I just hard-coded the conversion to camelCase instead).
Now I'm running on Sails 1.1.0-46, Sails-Json-Api-Blueprints 0.16.0, and with the SAME code as I posted above (I gave it another try), the error changed to:
{ "name": "UsageError", "code": "E_INVALID_NEW_RECORD", "details": "Missing value for required attribute firstName. Expected a string, but instead, got: undefined" }

Any ideas?