bttf

hello; i've tried triggering re-renders within my app and have done so several ways but react-sight is still unable to latch on. is there any method you'd recommend to help...

@tngan Has there been any update on this? I've run into a couple clients who used keycloak and have been bit by this. I'd be happy to submit a PR...

@tngan I'm also experiencing this issue. The SAML metadata I have has only one `md:SingleSignOnService` specified, and the binding for it is `urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST`. Stepping through the code, it seems that...

```xml redacted urn:oasis:names:tc:SAML:2.0:nameid-format:persistent urn:oasis:names:tc:SAML:2.0:nameid-format:transient urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress ```

@tngan Using [email protected] ``` TypeError [ERR_INVALID_ARG_TYPE]: The "url" argument must be of type string. Received type object at Url.parse (url.js:154:11) at Object.urlParse [as parse] (url.js:148:13) at buildRedirectURL (/Users/bttf/dev/my_app/node_modules/samlify/src/binding-redirect.ts:55:25) at Object.loginRequestRedirectURL...

@tngan I believe so. I think this was a mistake on my part

I've experienced the same with official leiningen 2.0 release. Did not happen with leiningen 1.7

ping @leafgarland @chaucerbao

> Left a few small nit picks - I'm comfortable with those being fast follows given the timeline. Thanks a bunch! Made those changes as requested.

High-level but is there a restriction or constraint that requires us to have models defined within `req.context`? It would be cleaner IMO to have something like `req.models`. It would also...