Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support observable definitions in patch extends #82

Closed
rmouritzen-splunk opened this issue Apr 3, 2024 · 0 comments
Closed

Support observable definitions in patch extends #82

rmouritzen-splunk opened this issue Apr 3, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@rmouritzen-splunk
Copy link
Contributor

rmouritzen-splunk commented Apr 3, 2024

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:

  • The profiles in the patching item are merged with the base item.
  • The attributes in the patching item are merged with the base item.
  • Observable definitions in the patching item cause an error, regardless of kind (top level object observable, attribute observable, or class attribute path observables).

With this issue we want to support merging the observable definitions from the patching item to the base item.

Related PRs:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

When branches are created from issues, their pull requests are automatically linked.

1 participant