Function at constraint different than function body at constraint about blaze_compiler HOT 2 CLOSED

I cannot replicate this. Maybe you're using an old version? We had a bug in
this area before.

On Sun, May 17, 2015 at 1:30 PM, Curtis M. Humphrey, Ph.D. <
[email protected]> wrote:

I have two cases:

functions:

• createOrUpdate(): next.exists() && prev.exists() || !prev.exists()
  schema:
  properties:
  menus:
  $user_id:
  $menu_id:
  properties:
  days:
  constraint: next.exists() && prev.exists() || !prev.exists()
  access:
• location: 'menu/$user_id/$menu_id'
• write: true

Which generates:

{
"rules":{
".write":"false",
".read":"false",
"menus": {
".write":"((false))",
".read":"(auth!==null)",
"$user_id": {
".write":"((false))",
".read":"(auth!==null)",
"$menu_id": {
".write":"((((newData.child('days').exists()&&data.child('days').exists()||!data.child('days').exists()))))",
".read":"((auth!==null))",
"days": {
".write":"(((newData.exists()&&data.exists()||!data.exists())))",
".read":"((auth!==null))"
}
}
}
}
}

However if I replace the constraint with the function I get a different
output. I don't understand, why?

functions:

• createOrUpdate(): next.exists() && prev.exists() || !prev.exists()schema:
  properties:
  dev: {}
  lists:
  type: object
  $list_name:
  type: object
  $list_item: {}

  menus:
  $user_id:
  $menu_id:
  properties:
  days:
  constraint: createOrUpdate()

{
"rules":{
".write":"false",
".read":"false",
"menus": {
".write":"((false))",
".read":"(auth!==null)",
"$user_id": {
".write":"((false))",
".read":"(auth!==null)",
"$menu_id": {
".write":"((((newData.exists()&&data.exists()||!data.exists()))))",
".read":"((auth!==null))",
"days": {
".write":"(((newData.exists()&&data.exists()||!data.exists())))",
".read":"((auth!==null))"
}
}
}
}
}

—
Reply to this email directly or view it on GitHub
#43.

from blaze_compiler.

closing, but please reopen if I am mistaken

from blaze_compiler.