Added the `META name value` keyword to the SETHOOK command.
Allows for adding metadata to a webhook. For example:
SETHOOK myhook http://endpoint/ META m1 12 META m2 13 NEARBY ...
Would result in notification that contain the "meta" element, which is
represented like:
"meta":{"m1":"12","m2":"13"}
Thanks for the suggestion @amorskoy
closed#105
Can now get back more details about an object:
NEARBY people FENCE ROAM people * 5000 SCAN :*
For more information see #96
Thanks @amorskoy for suggesting feature in #93Closes#96
It's now possible to mask the fence notifications based on the
command. For example, if we only want "set" and "del" commands.
NEARBY fleet FENCE COMMANDS set,del POINT 33 -115 10000
Suggested by @amorskoy, closes#99
JSET key id path value [RAW]
JGET key id path [RAW]
JDEL key id path
Allows for working with JSON strings, for example:
JSET user 901 name Tom
JGET user 901
> '{"name":"Tom"}'
JSET user 901 name.first Tom
JSET user 901 name.last Anderson
> '{"name":{"first":"Tom","last":"Anderson"}'
JDEL user 901 name.last
> '{"name":{"first":"Tom"}'
All commands use the GJSON path syntax, for more information:
Setting JSON: https://github.com/tidwall/sjson
Getting JSON: https://github.com/tidwall/gjson
This addresses an issue #73 that @huangpeizhi discovered while using
Tile38 in production where AOFSHRINK sometimes corrupts the database
causing the server to not start the next time.
Removed map[string]interface{} for Feature type.
Replaced "encoding/json" with "tidwall/gjson" for parsing.
Removed ablility to serialize to binary. JSON only.