Massimiliano Mirra
Massimiliano Mirra
@mattpocock. Wow, that was fast. Going to try it soon!
I haven't been able to break it so far. Context is narrowed correctly and plenty other things that would have caused a runtime error fail early with a sweet type...
> @bard That 'any' thing is to do with the test suite - it rimraf's the entire node_modules dir, npm installs it again and rebuilds the types from scratch. This...
Hmm, wondering how that would look like. What would you infer them from?
Two thoughts: 1) Would it work also when you are changing the context based on the previous context? ```ts { actions: { changeContext: assign((context, event) => { return { ...context,...
@abstractj this looks entirely distinct from #524. @devopsix I'm facing the same problem, did you find a workaround?
In case someone stumbles on this, this is how I worked around the issue in docker-compose. Let's say that the keycloak container is reachable from outside the stack as `keycloak.localtest.me`...
Thanks @abstractj. My scenario is the same as OP's second case above, where gatekeeper and the browser access keycloak through different URLs, respectively the private (LAN) and public (Internet) one....
@semenInRussia just a note to let you know that I haven't forgotten about this. I'm refactoring run-command to a better architecture and that will, among other things, make it straightforward...
Hey, yes, sorry for neglecting to update the issue myself, in the mean time I started using https://codeberg.org/ideasman42/emacs-elisp-autofmt and it fit the bill.