diff options
| author | Evan Read <eread@gitlab.com> | 2019-02-18 12:36:13 +0300 |
|---|---|---|
| committer | Achilleas Pipinellis <axil@gitlab.com> | 2019-02-18 12:36:13 +0300 |
| commit | 47fb1c5235236c8e28bfdc87b013419ae1d85dc8 (patch) | |
| tree | 0152ff66b8da3b175ed3f499aa52b039571c30a6 /doc/development/policies.md | |
| parent | 951e89127661150cdc23b8806085934ffdc4640f (diff) | |
Remove consecutive blank lines from markdown files
For the sake of consistency, removes any extraneous
consecutive blank lines from the doc suite.
Diffstat (limited to 'doc/development/policies.md')
| -rw-r--r-- | doc/development/policies.md | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/doc/development/policies.md b/doc/development/policies.md index e286c605438..6a3b90f3604 100644 --- a/doc/development/policies.md +++ b/doc/development/policies.md @@ -8,7 +8,6 @@ The policy used is based on the subject's class name - so `Ability.allowed?(user Permissions are broken into two parts: `conditions` and `rules`. Conditions are boolean expressions that can access the database and the environment, while rules are statically configured combinations of expressions and other rules that enable or prevent certain abilities. For an ability to be allowed, it must be enabled by at least one rule, and not prevented by any. - ### Conditions Conditions are defined by the `condition` method, and are given a name and a block. The block will be executed in the context of the policy object - so it can access `@user` and `@subject`, as well as call any methods defined on the policy. Note that `@user` may be nil (in the anonymous case), but `@subject` is guaranteed to be a real instance of the subject class. |