mirror of
https://github.com/google/go-jsonnet.git
synced 2026-04-06 22:11:31 +02:00
8d4b3b72ab
This follows the same pattern as I used for the C++ implementation. Flattening the object is probably also possible, but I think it would involve binding references to 'super' iff they are satisfied by fields in existing ancestors and leaving them unbound if they're unsatisfied so that they can be late-bound by extending the output object. That seems at least as complicated as defining a new form of uncachedObject to represent a key-removal operation. For https://github.com/google/go-jsonnet/issues/830
14 lines
335 B
Plaintext
14 lines
335 B
Plaintext
RUNTIME ERROR: Field does not exist: x
|
|
-------------------------------------------------
|
|
testdata/builtinObjectRemoveKey_super_assert:2:10-16 object <o1>
|
|
|
|
assert self.x : 'x',
|
|
|
|
-------------------------------------------------
|
|
Checking object assertions
|
|
|
|
-------------------------------------------------
|
|
During manifestation
|
|
|
|
|