You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Expected behavior is data in conditionResolver function would be the same type passed in the context.
I'm assuming this is from the fact that the matchConditions function uses getValueFromPath which is set to return string, as it returns `${value}`, as opposed to value, as seen here:
Hi @yaser-ali-s, already made a change for that. I would like this package life on its own, that's why it doesn't have dependencies. Thank you for notice this issue.
Running the following code:
Yields the following:
typeof data string typeof expected boolean matchConditions false
This would be fine except in
types.ts
the following is set:Expected behavior is data in conditionResolver function would be the same type passed in the context.
I'm assuming this is from the fact that the
matchConditions
function usesgetValueFromPath
which is set to return string, as it returns`${value}`
, as opposed tovalue
, as seen here:Is there a reason as to why it is always returned as string? What else does it affect?
I would like to suggest using lodash's property function, as you can't go wrong with it, and it's already quite efficient.
You can even change the applyContext function to utilize the template function provided by them.
The text was updated successfully, but these errors were encountered: