Dave MacLeod

Interesting issue, noticed a few things: - The original schema doesn't work but does if you constrain on just ``@date`` (and reproduces the error) - I think this is an...

> You're correct that the original cast suggestion won't work, even if it references the property correctly, but I wasn't sure how sophisticated and bespoke those suggestions could be. Yeah,...

> Love what you're doing with these, @Dhghomon. A few things I wanted to ask about: > > ``` > Note: The following functions may help you convert from array...

I'm just starting to look at the CLI myself so still a bit unfamiliar but here are some questions and thoughts: - I assume this error is happening right away?...

Not that I know of: the only part where I see a backtrace in the code is inside interrupt.rs which is for something else. This does give a sort of...

Works for me after `cargo update` too. Before that there were some random errors about a `Revisioned` trait not being in scope.

Oh yeah, I've just been living with this small annoyance without it reaching the conscious "Maybe I should fix it" level. Will take a look

Going to close this as looks like the migration tool now emits a `No schema changes detected` so it's smart enough to recognize that adding the keyword `optional` isn't actually...

> Ugh, this is still broken if there is a subtype of Node. > > It also probably _should_ detect a change. There's no semantic change, but we do distinguish...

Hi @3rly , looks good to me but then again I don't know anything about Bash so my "looks good to me" really doesn't mean much! @AlexanderWillner , do you...