Blaž Hrastnik
Blaž Hrastnik
We weren't able to use `anchor build --verify` on the CI because it expects to spawn it's own Docker container, but it's already running in a container. It ends up...
I've used `tarpaulin` before, but none of these tools can be used with Anchor integration tests since these run contracts on an actual validator node (inside a BPF VM).
Seems to have completely broken CI, I'm reverting.
I have report fuzzing here: https://github.com/smartcontractkit/chainlink-starknet/issues/164 It's hard to make it not panic by always generating valid report lengths + valid felts
http://fontello.com/ for building a custom icon set composited from other sets.
We used to default to anywhere on the line but what if there's multiple diagnostics on a single line?
Union: put_cursor should be enough for extending downwards with the extend flag, it'll move the head but retain the anchor. For extending upwards, construct a new range for the sibling...
We have an undo tree internally with support for :earlier :later. We just don't have a good way to visualize the tree
I disagree with this / this should be split into two separate issues. > The current picker is pretty fancy, too fancy actually. It's the most minimal UI we could...
This should probably happen in the devnet