Jan Špaček
Jan Špaček
For other people who hit the same issue, a workaround is to use version 1.1 of this crate.
This is interesting! What kind of boilerplate clients encounter? What kind of features should make our hypothetical client API different from a generic HTTP library? The routing PR #1618 evolves...
Hmm, I understand that `Blob` looks better than `ArrayBuffer`, but there might be other reasons for using `ArrayBuffer`. For example, a `Blob` does not have to be a memory buffer...
> The `ChiselEntity.save()` method is already `async` converting to `ArrayBuffer` is not a problem. Yes, we will have to do the translation `Blob` -> `ArrayBuffer` in JavaScript, but we don't...
This is related to issue #1739
I think that SQLite does support unique index with multiple columns: https://www.sqlite.org/lang_createindex.html ``` sqlite> create table types (name text, api_version text); sqlite> create unique index i on types (name, api_version);...
Or we could simply use `(api_version, name)` as the primary key in the `types` table, so that we don't have to keep track of type ids in `chiseld`.
The #1618 PR modifies the current behavior as follows: - When `chiseld` is started with `--debug` (which is automatically used by `chisel dev`), then the 500 HTTP response contains a...
This particular code in `chiseld` is a hack and we should rewrite it, but in my opinion we should not allow the user to change the names of these directories...
Indeed! If we have merged #1618, the problem in `chiseld` would be solved...