Add EX and PX options to JSON.SET

[gkorland]

Ref #415

[codecov[bot]]

Codecov Report

Base: 81.36% // Head: 81.36% // No change to project coverage :thumbsup:

Coverage data is based on head (b458d28) compared to base (b458d28). Patch has no changes to coverable lines.

:exclamation: Current head b458d28 differs from pull request most recent head 435cd84. Consider uploading reports for the commit 435cd84 to get more accurate results

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #913   +/-   ##
=======================================
  Coverage   81.36%   81.36%           
=======================================
  Files          15       15           
  Lines        3896     3896           
=======================================
  Hits         3170     3170           
  Misses        726      726           

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

[bjwschaap]

Any indications on as when this will be merged?

[PaulAtkins88]

bump on this PR

[timeimp]

I was expected a 1:1 match with the SET command for JSON.SET - imagine my confusion when the EX value was never accepted!

Is there an outstanding item preventing merge? Would really like to see this normal EX value be set on JSON.SET commands