Noah Zachary Gordon

Right now it looks like the `Debug.log` function simply calls `toString` on the second argument (the value being logged) and appends it to the first argument. Would it be reasonable...

Sounds like a cool idea! Perhaps we could start working on an `elm-debug-extra` or `elm-developer-console` library in order to expose more of the Console API?

@obmarg the rationale here is that a `clientResource` is only supposed to be a resource generated by the client, which does not have knowledge of the IDs present on the...

I also know that this kind of functionality isn't really useful unless you can modify the attributes and relationships of an existing Resource, so I'll get to work on that...

What's the use case here? I'm hesitant to add another layer of types as it makes the return value a bit clumsy to handle. Right now there are two ways...

@97jaz As I understand it this is not a parsing error; you can successfully apply the `document` decoder to the payload and get back an Elm type that you can...

@97jaz if that's the case then it's certainly a high-priority change! The document shouldn't fail to parse because of an empty relationship. I'll look into this when I have a...

According to the spec, the relationships must contain *at least one of* data, links or meta. That means the above is a valid JSON API document. If it's failing to...

@dawehner I like this! I'm toying with the idea of unifying around a `JsonApi.Http.Request` type which would incorporate most of this functionality.

@dawehner because "JSON API is agnostic about the strategies supported by a server," we are more or less forced to model the filter as a string. ``` withFilter : String...