Jouke van der Maas

First, I think the Ember project deprecates things far too frequently for this to be a good idea. Just scrolling through the 3.x deprecations many of them are just removing...

@chriskrycho Thank you for the response. Let me first emphasize that I think the Ember core team has done a great job over the years. We've been using Ember since...

@runspired I think most addons are way less complicated than ember data is (and have less baggage), so it's worth keeping that in mind too. My personal opinion has always...

@lolmaus we decided not to use github pages because (1) this was an internal addon and we already have deployment infrastructure and (2) I couldn't be bothered to figure out...

@terencefan thank you for the reply. We have indeed settled on that solution. However, the connection string is shown in Azure Portal. Currently it shows both the key and the...

Seems that this is the case for any "falsy" value, e.g. the boolean value `false` also has this effect.

Will this lead to breaking changes? If so can we make an effort to document them with a clear migration path?

The solution in the serializer was to use this 'contract resolver': https://github.com/joukevandermaas/saule/blob/master/Saule/Serialization/JsonApiContractResolver.cs (see #132). I'm guessing we could do the same for the deserializer.

That would be great!

@esotery I'm still very open to a PR!