Tijmen van de Meent
Tijmen van de Meent
I wrote a fix for this issue in #2416, but it's still waiting for approval before it can be merged.. I think the maintainers are mainly focusing on other projects...
I tried to find why the second fault , the failed import `@import "@esri/calcite-components/dist/calcite/calcite";` didn't work, and I found out that changing it to `@import "@esri/calcite-components/dist/calcite/calcite.css";` actually solved that part...
Hmm, perhaps I didn't check it well enough. I removed both options just to be sure, and that fixed it, but I guess I didn't verify which of the 2...
We ran into this problem to, so we reverted to v4.x.x for now. Would be nice if this could be solved in v5 though
We're still running into this as well. However, reading through the OpenAPI specification, it seems as though this is actually expected behaviour. The `null` value should be included in the...
@Jackman3005 yes, that's right. I agree that it doesn't feel right, but according to the clarification that's how it should be specified. However, I did some digging and found some...
I'm fine with giving this a try myself by the way, seems like an interesting challenge.
I've rebased the branch so it'd be up to date with the latest version on `main`, it still needs another review
I've just recently used this: if you use the `Authorization` tab, and select `Bearer token` authorization, the token you paste will be placed in the `auth.token` field in the handshake....
It's a semi-arbitrary number, with a minimum of 1 and a maximum of 4 handles.