Matthew Nibecker

We already have support for the spread expression in arrays, set and records. This support should be extended to maps as well.

I'm going to do a quick pass on the api docs to update them but remove the detailed information about response payloads. This issue is a place holder to revisit...

Optimize filters on pool keys

1

If a user is filtering on a pool key field (i.e. `ts >= now()-3h`, the optimizer should recognize this and limit the range of scanned data.

zed: Support git-like HEAD reference

1

As seen in git, we should add the ability to specify `HEAD` and `HEAD~#` when referring to commit ids.

Ability to bucket time by months

1

This could also include other variable time lengths such as year or weeks in a year.

You should be able to cast time as a duration (or probably any other number since time is nanoseconds since epoch). I stumbled this while trying to find the duration...

This could be implemented by have the result of `t1 - t2` getting set as a duration, though I'm not sure what this would mean for other operands. Could also...

I'm sure this reasoning could apply to other areas in the code base... but it seems if you want `websocket` to mimic its real life counterpart, all the functionaliy inside...

For version 2.0.0: If you call `server.close()` somehow `websocket.readyState`gets set to undefined. `readyState` should be set to 3 or `WebSocket.CLOSED`. I wrote a little mocha test to verify this bug:...

Parse regular expressions outside of the search context as string literals. Close #4148