Sævar Berg

> @Axedyson, the issue seems to come from the inference that `cache.updateQuery()` is doing based on the query definition and the data that you pass from `result`. That doesn't sound...

@devongovett > It's not a limitation we wanted, just a technical trade off required by internal implementation details. React actually makes it extremely difficult to build components that are aware...

I'm also having this issue. I will assume that the other's reproductions are enough. Next: 14.2.5 @nextui-org/link: 2.0.34 Even something as simple as the below still demonstrates the issue. ```ts...

@awesome-pro I have tried deleting `node_modules`, tried building and running the production build, etc. The problem still persists. I will see if I can create a real, isolated reproduction later...

I've just encountered this issue. I've also tried to use the `Loading` item described in the docs, but that has no effect. Are there any plans on fixing this, or...

I've found a workaround which is just maintaining the selection state yourself on `Command`, and when data changes, you just set it to the first element in the list.

I also just ran into this same issue when going from 2.0.5 to 2.3.0. In particular, this happens when calling `builder.toSubgraphSchema`. The primary motivation for this upgrade was getting support...

> Hi. We're closing some old issues as outdated. If this is still relevant, leave a message, we'll reopen it. Thank you. Appreciate your contribution to the project - shadcn...