Skip to content

Commit d256401

Browse files
committed
fix(docs): incorrect information for grapple.scope_definition type
1 parent 34b8f47 commit d256401

File tree

1 file changed

+2
-3
lines changed

1 file changed

+2
-3
lines changed

README.md

+2-3
Original file line numberDiff line numberDiff line change
@@ -1087,12 +1087,11 @@ Used for defining new scopes.
10871087
- **`name`**: `string` scope name
10881088
- **`resolver`**: [`grapple.scope_resolver`](#grapplescope_resolver)
10891089
- **`desc?`**: `string` scope description (default: `""`)
1090-
- **`force?`**: `string` scope description
1090+
- **`force?`**: `boolean` scope fallback
10911091
- **`fallback?`**: `string` fallback scope name
10921092
- **`cache?`**: [`grapple.cache.options`](#grapplecacheoptions) | `boolean`
10931093
- **`priority?`**: `integer` scope priority, higher scopes are loaded first
1094-
- **`hidden?`**: `integer` do not show the scope in the [Scopes Window](#scopes-window)
1095-
- **`delete?`**: `integer`
1094+
- **`hidden?`**: `boolean` do not show the scope in the [Scopes Window](#scopes-window)
10961095

10971096
**Note**: Scopes are given a `priority` based on their fallback ordering. By default, scopes without a fallback are given a priority of `1000`; scopes with a fallback, but are also fallbacks themselves, are given a priority of `100`; and all other scopes are given a priority of `1`. Higher priority scopes are loaded first. This can be overridden by setting a scope's `priority` manually in the [settings](#settings).
10981097

0 commit comments

Comments
 (0)