Nicolas Goudry

I found what’s triggering this behaviour. On docsify’s `afterEach` hook, the `div` holding theme switch button is added **before** page content. This prevents docsify to detect that a custom page...

@petermicuch I think this is clearly related. My weave pods also use `nft` backend as confirmed by running: ```shell $ kubectl exec -it [weave_pod] -- iptables -V iptables v1.8.3 (nf_tables)...

Personnellement, je trouve le terme `fourche` bien plus parlant que `scission`. Exemple : On parle couramment de fourches pour les lignes de métros qui se séparent à un endroit sur...

@Szymongib Thanks for your quick reply. Regarding the workaround, your proposal is valid, but as of `v1.14.0` I would still need to create another Ingress object than the one created...

Hi, not sure this is related but I have a similar issue. I’m using React 17 and use lazy-loaded routes. The issue is happening with a font awesome SVG icon....

Seems a great suggestion, but how would you design it? It can't be a mandatory behaviour anyway, so maybe through a boolean prop we would refresh the access token automatically...

@andrijan Yeah this happens because you didn’t implement `triggerLogout`, I will make a check for `onLogoutSuccess` or `onLogoutFailure` before forwarding this prop. About the second bug, I don’t understand, which...

Oh yeah, this sample didn’t took account of `triggerLogout` being forwarded so that’s it... Sorry. Will be fixed soon, as well as `README.md` :+1: Regarding logout process implementation, you will...

@andrijan @Amurmurmur When you call `triggerLogin`, HOC component will have it’s internal state prop `isFetching` set to true **before** calling SDK’s `login` function. Therefore if you call once again `triggerLogin`,...

So what's the deal? Can you show us both code samples please? See what's causing this, thx