Glauber Costa

native date types

1

Works on my tests, probably doesn't work very well with nested types.

Allow option to use frontend types

5

Our `exports ChiselEntity` way of coding is convenient when chiselstrike is standalone. But when there is a frontend involved (the common case!!), they may already have types in that app...

we should have a way of undoing changed that break the schema

1

It doesn't matter how careful we are, there will always be changes that end up preventing chiseld from start. One recent example is #1605, that passed the apply cycle tests...

ChiselStrike is essentially single-threaded (at least on MacOS)

2

This is the case at least on the mac, maybe it works on Linux. It could be because of SO_REUSEPORT's behavior on Mac, in which case this is actually totally...

did we fail ? did we succeed? it returns nothing so it is very hard to react to what it did. I think it should return number of rows deleted...

missing dead simple way of allowing build-from-source to use npx

2

Users building from source should be able to test chiselstrike with a workflow as similar as possible to our documentation, meaning `npx` installs, etc. If that's not possible, the alternatives...

inform users of failures on transaction failure

1

If we don't return an error code if a transaction fails, we may end up in a situation where the user sees an error code 2xx indicating success, but ultimately...

ChiselStrike extension system

1

# ChiselStrike’s plugin system ChiselStrike allows frontend developers to deploy their backends from typescript code. But what if some specialized functionality is needed, that falls outside of the realm of...

We duplicate some of the information on the README into lib.rs so it can show nicely on crates and docs When we patched the README to reflect the current status...

Add _createdAt and _updatedAt fields

1

This PR adds _createdAt and _updatedAt fields. We will establish a rule, that we now check, that ChiselStrike internal entities should start with an underscore.