Add support for defining observables in "patch extends" #83
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently observable definitions are flagged with an "unsupported" error for the patch extends case.
A patch extends is triggered when a class or object (most usefully an extension class or object) is defined with an extends property that refers to a class or object in the core schema, and either the name matches the extends or it doesn't have an extends. This patch allows modification of the class or object in the extends property as shown below, and then the patching item disappears (it isn't added to the schema).
A patch currently does these things:
With this issue we want to support merging the observable definitions from the patching item to the base item.
Fixes issue #82.
Related to PR ocsf/ocsf-validator#19.