yetitwo
05/31/2022, 6:34 PMJoey
05/31/2022, 6:36 PMJoey
05/31/2022, 6:36 PMSingha1
05/31/2022, 6:37 PMJoey
05/31/2022, 6:37 PMJoey
05/31/2022, 6:37 PMSingha1
05/31/2022, 6:52 PMJoey
05/31/2022, 6:59 PMJoey
05/31/2022, 7:01 PMAkshat
06/01/2022, 7:35 AMRupa
06/01/2022, 8:15 AMwilliamdclt
06/01/2022, 12:41 PMJake
06/01/2022, 12:42 PMJake
06/01/2022, 1:00 PMyetitwo
06/01/2022, 3:52 PMzed schema write
and zed validate
having different shapes), so I've written a script that sticks them together in a tempfile. This works, but when I went to add comments to my schema, the validations started failing. I can reproduce if I create a validations file that has a schema with comments. Something like this will trigger it:
schema: >-
// This is a user
definition user {}
relationships:
assertions:
assertTrue:
assertFalse:
validations:
which errors. is that expected behavior?Joey
06/01/2022, 3:52 PMJoey
06/01/2022, 3:53 PMyetitwo
06/01/2022, 3:53 PMā spicedb git:(main) ā zed validate validations.yml
Error: error when parsing schema: Unexpected token at root level: TokenTypeKeyword
Joey
06/01/2022, 3:56 PMJoey
06/01/2022, 3:57 PMJoey
06/01/2022, 3:57 PMJoey
06/01/2022, 3:57 PM{ schema: '// This is a user definition user {}',
relationships: null,
assertions: { assertTrue: null, assertFalse: null },
validations: null }
Joey
06/01/2022, 3:57 PMJoey
06/01/2022, 3:57 PMschema: |
yetitwo
06/01/2022, 4:04 PMyetitwo
06/01/2022, 4:04 PMyetitwo
06/01/2022, 4:06 PMrelationships: >-
Joey
06/01/2022, 4:06 PMJoey
06/01/2022, 4:06 PMyetitwo
06/01/2022, 4:06 PM