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
so that we can use string for boolean values instead of just true or false
Expected:
enabled: "true" # or true, "t", "yes", "y", "1" should be converted as true
Actual: only enabled: true is supported.
This is a minor improvement, I thought the following config below would work with the changes from this issue, however, it does not work as the variables processor does not kicks in (hooks) on the teracy-dev-kernel extension config (Maybe we'll think about this later to make this possible).
hoatle
changed the title
should always use Util.boolean for boolean values
should always use Util.true? or Util.boolean for converting boolean values
Oct 16, 2018
hoatle
changed the title
should always use Util.true? or Util.boolean for converting boolean values
should always use Util.true? for converting boolean values
Oct 16, 2018
hoatle
added a commit
to hoatle/teracy-dev
that referenced
this issue
Oct 16, 2018
so that we can use string for boolean values instead of just
true
orfalse
Expected:
enabled: "true" # or true, "t", "yes", "y", "1"
should be converted astrue
Actual: only
enabled: true
is supported.This is a minor improvement, I thought the following config below would work with the changes from this issue, however, it does not work as the variables processor does not kicks in (hooks) on the teracy-dev-kernel extension config (Maybe we'll think about this later to make this possible).
The text was updated successfully, but these errors were encountered: