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

Merge reusable location lists when merging schemas #751

Merged
merged 5 commits into from
Apr 6, 2020

Conversation

marshallmain
Copy link
Contributor

This PR further enhances the generator's custom schema capabilities. It allows custom schemas to extend the list of locations that a set of official ECS fields is are reused at. For example, hash is a fieldset that would often be useful to include in custom schemas. With this PR, users can define a custom schema file with name: hash and add more locations where hash should be reused in their custom schema.

@webmat webmat added the 1.6.0 label Mar 25, 2020
Copy link
Contributor

@webmat webmat left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is works well, thanks for submitting this, @marshallmain! I'll merge as is.

In trying it out, I've noticed an undesirable behaviour that comes from before this PR. When creating a custom schema, and trying to nest hash under it, I found that I had to redefine things I had no intention to change in the custom "hash.yml" field set I used, in order to nest it under my custom schema.

We could eventually change at which point a field set is being validated, to improve on this. Hit me up if you're interested in looking into this ;-)

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

Successfully merging this pull request may close these issues.

2 participants