You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/errors.md
+2-18Lines changed: 2 additions & 18 deletions
Original file line number
Diff line number
Diff line change
@@ -1,24 +1,8 @@
1
1
# Errors
2
2
3
-
Depending on your operation, your object transaction may fail. This details the reasons
4
-
5
-
In this context, value means either "member of object" or "index of array"
6
-
7
-
## Get
8
-
9
-
-`ERROR_NOT_FOUND`
10
-
- Attempted to access a value that does not exist
11
-
-`ERROR_VALUE_INCORRECT_TYPE`
12
-
- Attempted to access a value that has the wrong type. This can happen if the query uses `.[30]` to get an array index, but an object exists instead. It can also happen if the user writes `get-string`, and it found a non-string value after evaluating the query. It can also happen if the user writes `set-string`, and the place to write the new value already has a value of a different type
13
-
-`ERROR_VOBJ_INVALID_TYPE`
14
-
- The virtual object (a string that contains a reference to the real global object) had keys with unexpected values. You shouldn't get this error unless something has seriously gone wrong
15
-
16
-
# Handling
17
-
18
-
Because Bash often does the wrong thing silently, it's important to fail early when any inputs are unexpected. `bash-object` does this at every level
19
-
20
-
Below, if any of the assurances do not pass, `bash-object` will fail with a non-zero exit code. For some of these, `VERIFY_BASH_OBJECT` must be a variable
3
+
Because Bash often does the wrong thing silently, it's important to fail early when any inputs are unexpected. Extra checks that require spawning subshells require setting the `VERIFY_BASH_OBJECT` variable. We recommend exporting it so any child Bash processes keep the verification behavior
0 commit comments