Added option in .env for allow_eval to be activated in jsonPath #177
Conversation
| ######################## | ||
| # Various Settings # | ||
| ######################## | ||
| ALLOW_EVAL=false |
There was a problem hiding this comment.
Let's call it ALLOW_JSONPATH_EVAL. Did you test it and it works well for you?
|
actually, filtering does not appear to be functional in the Ruby implementation of jsonPath... Evaluating similar data with http://ashphy.com/JSONPathOnlineEvaluator/ gives the correct results, but using the same path expression generates errors like this: |
|
bleh. needs more investigation, will try to look into it this weekend |
|
There we go! |
|
What was the problem? |
|
Hrm, jsonPath still doesn't seem to be working. Need to try the ruby gem by itself I think. But the env variable name is changed now |
|
Yea, I'm curious what the raw behavior of the gem is. |
|
@snicker What should we do with this? |
|
Hm... not sure what caused the failing build. All this does is enable the option for allowing the JSONPath eval in the .env, I'd guess that it's safe to merge and doesn't need any specs. The issues I was experiencing seem to be related to the gem itself and need some more investigation (that I haven't done) Do with it what you will... |
No description provided.