Joe Marty

That looks pretty good to me! I was going to suggest something similar. Might be nice to use something more specific than `object` to compare it to (I'm not sure...

Ahhh shoot - you're right! Actually it shouldn't be too bad though - mostly we'd just have to replace `fakeClient` stubs in the `beforeEach` blocks with stubs of `selectElement` to...

But just to validate your assessment - I agree! You're on the right track with what it *should* look like, and I think that plan is better than trying to...

I'm afraid I'm not using Node in any of my current projects anymore, so I don't have the resources to collaborate on this much at this point 😞 But at...

Ooh, I see what you're saying about no.1 - yeah you'd just have to experiment with what useful info the error message has access to in that case... If nothing...

Elm doesn't prevent you from using cookies. If your server sets a cookie in the response header, the browser will include that cookie in future requests for that domain until...

Interesting conversation! @clintonb So, when you talk about the need to "share data across services on different subdomains" are you talking about basically having an Elm app make API requests...

@justgage, If you're storing your JWT in a cookie, the Elm app shouldn't need to know anything about it, right? (The browser will automatically send the JWT with every relevant...

I suppose if you want to get the current user ID in your app it *could* make sense to pull it out of the cookie. But I can't think of...

Now that's an interesting case! I don't know haskell, so have never used haskell-servant or servant-auth, but that's an odd authentication scheme! I took a look at the README here:...