Marco Leko

Seems effect more people, also experiencing this with the latest version (2.6.8), however doing: `curl service-name.namespace` at least seems to work

People can't state that the approach of reactive Forms is usable, while showing an example with template driven Forms. Its the same like I came to buy for my new...

Unfurtunately the only workaround for this is skip the test 🤦🏻‍♂️ Sorry to say this. Is unfurtunate, that noone is reacting to this

Is there any progress on this? I am also facing the same issue and put up a question with all relevant infos here: https://stackoverflow.com/questions/64026278/react-jest-rtl-check-if-element-is-not-visible Btw. react testing library only reacts...

Unfurtunately our project runs on a custom micro-frontend architecture, splittet across multiple private coporate repositories :/ Im sorry for this, usually having something reproducable eases up way more the bug...

Hey guys so I extended the bug report with the server part and more details to the entry component part of the code-base. The main differences that I can see...

I tried to make a code-sandbox wie a similar process to what we currently have, by dynamically requiring the client entry bundle in the server and pass it to `getServerState`....

hmm it is really unfurtunate that it only works like this :/ The server part of our micro-frontend (called backend for frontend) is strictly decoupled from the client of the...

Referring to your comment: Im wondering by checking our `node_modules` there is only one version of `react-instantsearch-hooks` in the `node_modules` (Usually packages might have their own `node_modules`, with specific versions...

Is there anything we can do about to make these changes mergeable? Seems like this PR got stale for a few months already