Unexpected implementation level of access rules. about blaze_compiler HOT 3 CLOSED

The rules cascading in that manner is intended. I believe to unlock the $parentId for writes, you'd need to use a $wilderchild. #46 is related.

from blaze_compiler.

Wilderchild will fix one issue but there is another bug I noticed last week
you are hitting. I will fix that today.

The rules cascading in that manner is intended. I believe to unlock the
$parentId for writes, you'd need to use a $wilderchild
https://github.com/firebase/blaze_compiler#wilderchild. #46
#46 is related.

—
Reply to this email directly or view it on GitHub
#56 (comment)
.

from blaze_compiler.

OK the bug I thought existed didn't. So

1. you need a wilderchild's on $childId to do nesting, as ginovva320 said, so ~$childId
2. wilderchilds are not properties, they are their own special commands so do not appear in the properties field. I have added some special error messages for detecting that case, as you are not the first to hit that unexpected behavior. (FYI it's to do with the JSONSchema spec)

Putting it all together I think this is what you want:-

schema:
  type: object
  additionalProperties: false
  properties:
    test:
      type: object
      $parentId:
        type: object
        ~$childId:
          type: object
          properties:
            timestamp: {type: number}

access:
  - location: /test/$parentId
    read:     auth.uid != null
    write:    auth.uid != null && prev.exists() == false

  - location: /test/$parentId/$childId
    write:    auth.uid != null && (prev.timestamp.exists() == false || next.timestamp >= prev.timestamp)

the better error message is in version 0.0.34

from blaze_compiler.