Skip to content
This repository was archived by the owner on Nov 17, 2017. It is now read-only.

Components subgenerators#24

Open
timroes wants to merge 3 commits intoelastic:masterfrom
timroes:feature/components
Open

Components subgenerators#24
timroes wants to merge 3 commits intoelastic:masterfrom
timroes:feature/components

Conversation

@timroes
Copy link
Copy Markdown

@timroes timroes commented Feb 20, 2016

Hi @spalger,

this branch has a first draft of a components subgenerator in it. It has a field format subgenerator, that can be called with yo kibana-plugin:field-format and will generate new files. Also it has the auto detecting feature in the main generator for field formats right now.

Every feedback highly welcome. If this is a base one could work of, we could create several subgenerators for the different components, link them up in the main generator and - imo - throw away the "old" sample components in the main generator.

@KlavsKlavsen
Copy link
Copy Markdown

Using this, would I be able to create a field format which translates numbers such as "4740" and "4730" into "4740 - account locked out" and "4730 - account unlocked" (windows EventID's ;) for a field names EventID ? or is that too specific. In my use case i could just harcode the list of EventID's to replace.

@timroes
Copy link
Copy Markdown
Author

timroes commented Mar 30, 2016

@KlavsKlavsen that is exactly what you could do with a field formatter. You could hardcode the list of ids (or even create a server interface to retrieve it from other documents) and then let the field formatter look up the id in the map you have and append it.

@KlavsKlavsen
Copy link
Copy Markdown

Looking forward to you merging this - now you have commit access ;)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants