feedback: box.schema.role.revoke() | Tarantool
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 15
- Forks
- 49
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 3
Description
Product: Tarantool
Root document: https://www.tarantool.io/ru/doc/latest/reference/reference_lua/box_schema/role_revoke/
SME: @ locker
Details
<…>
box.schema.role.revoke()|box.schema.role.revoke(role-name, privilege, object-type, object-name)
Отмена прав роли.
Параметры:
role-name (string) – название роли
privilege (string) – „read“ или „write“ или „execute“ или „create“ или „alter“ или „drop“ или их комбинация.
object-type (string) – „space“ или „function“ или „sequence“ или „role“.
object-name (string) – имя функции, спейса, последовательности или роли|.Должна существовать роль, должен существовать объект, но оши<…>
https://www.tarantool.io/ru/doc/latest/reference/reference_lua/box_schema/role_revoke/
Missing options ({if_exists = true}) as fifth argument yet supported at least since 1.6.5
Definition of done
- Add
if_existsparameter to box.schema.role.revoke() - Check formatting
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked box.schema.role.revoke() root document and compare its signature and parameter list with the supported fifth argument, {if_exists = true}. Add the missing parameter and check the page formatting; done means the reference documents the supported option accurately.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 52/100