Permission named use failing validation when used along import keyword

[jfdufourupgrade]

Is using use as a permission name allowed? The validation behaviour is different depending if we also have the import keyword or not in the schema file...

• example.zed

import "whatever.zed"

definition my_definition {
  relation user: login

  permission use = user
}

definition login {

}

(The whatever.zed file is empty)

Running zed validate example.zed will produce error:
ERR terminated with errors error="parse error in ``, line 6, column 14: Expected identifier, found token TokenTypeKeyword"

• example2.zed

definition my_definition {
  relation user: login

  permission use = user
}

definition login {

}

Running zed validate example2.zed will produce success
Success! - 0 relationships loaded, 0 assertions run, 0 expected relations validated

• example3.zed

import "whatever.zed"

definition my_definition {
  relation user: login

  permission use_potato = user
}

definition login {

}

Running zed validate example3.zed will produce success
Success! - 0 relationships loaded, 0 assertions run, 0 expected relations validated

[jfdufourupgrade]

client: zed v0.33.1

[tstirrat15]

Ah, yeah. In the new schema parser (which is what the Composable Schema functionality uses), use becomes a keyword, because we use it in directives at the top of the file, a la use expiration;.

I've documented it here: https://authzed.com/docs/spicedb/modeling/composable-schemas#breaking-changes

But I omitted use as one of the new keywords. I can make that change to the docs.