Mathew Polzin

@Gabriella439 I know just a small amount about the strategy for accepting changes into the Dhall language specification (e.g. voting amongst those with Dhall implementations native to another programming language);...

Thanks for the feature request and offer to help implement it! I don't currently have a roadmap for v1.1 support. I also don't have plans to add full v1.1 support...

Although it could be argued that this feature request isn't "fancy" I would say it falls under the CONTRIBUTING guidelines' "unlikely to be accepted" entry worded as follows: > Fancy...

I imagine the idea is to omit a certain property when it is empty (i.e. unused), or is the goal to sometimes remove populated properties in the response payload?

So is the goal is to omit based on which `View` is used or based on something found in the `data` or `Plugn.Conn`? I wonder if this could also be...

> I suppose I can by pointing my flake.nix to the fork in this pr, right? Yup, e.g. (for a flake config) ```diff - nix-darwin.url = "github:LnL7/nix-darwin"; + nix-darwin.url =...

This is interesting. Fundamentally the JSONEncoder passed in is used as sparingly as possible during reflection, but I can see how you would want (and reasonably expect) the encoder's settings...

This library focuses on handling the response body (decoding to errors, data, metadata per the `JSON:API` specification). Since a `204` response has no response body, there's nothing to decode using...

My reading of the JSON:API specification has always left this as an implementation detail. In my reading, a **relationships object** (plural) must contain keys which are each valid **relationship object**s...

@Enzime I hope you don't mind if I ping you on this to get your thoughts. Not my PR but configuring power management would be nice for me now that...