[Drilldows] Url Drilldown basic template helpers

[Dosant]

Summary

close #77758

New helpers

Provides a basic list of string manipulation helpers for URL Drilldown templating:

Helper	Description
formatNumber	A wrapper around elastic/numeral-js. Allows to format number, currencies, bytes and etc... {{formatNumber value "0.0"}}
lowercase	transform a string to lowercase string
uppercase	transform a string to uppercase string
trim
trimLeft
trimRight
left	{{left "12345" 3}} -> "123"
right	{{right "12345" 3}} -> "345"
mid	{{mid "12345" 1 3}} -> "234"
concat	concatenates list of values into a string: {{concat value1 ";" value2 }}
replace	Can be used to replace a substring with another substring. Replaces all occurrences. {{replace "Label:Feature:Something" "Label:" ""}} -> "Feature:Something"
split	Splits a string using a splitter character {{split "Label:Feature:Something" ":"}} -> ["Label", "Feature", "Something"]

Checklist

Delete any items that are not applicable to this PR.

• Documentation was added for features that require explanation or tutorials - Will add use facing documentation when we agree with the list
• Unit or functional tests were updated or added to match the most common scenarios

For maintainers

• This was checked for breaking API changes and was labeled appropriately

[elasticmachine]

Pinging @elastic/kibana-app-arch (Team:AppArch)

[elastic-jb]

This is a great set to handle most simple string manipulations. I think we may want to still consider a way for a developer to register a custom helper if it's useful for them, but that is a separate goal.

[Dosant]

a way for a developer to register a custom helper if it's useful for them, but that is a separate goal.

@elastic-jb 👍 this is tracked here: #78404

[elastic-jb]

I think we need the change for event.row (79157) to make use of the numeric formatting. I can't create a drilldown on a table that only has an aggregation, and if I add a terms aggregation to act on, I can't access the 2nd column value. That does bring up a point though. Even if I have a single column table with an aggregation, I would expect the context menu to display and allow me to send that single value. There is no way to do it right now.

[Dosant]

@elastic-jb,

That does bring up a point though. Even if I have a single column table with an aggregation, I would expect the context menu to display and allow me to send that single value. There is no way to do it right now.

Correct,
That is because for Drilldowns triggers we reused what already existed for filters.
We didn't create a filter from an aggregated value from a table, so drill-downs inherited this limitation :(
I think this has to be improved in scope of #78289 which we planned for 7.11 work.

Regarding the current pr and helpers: this future table-vis work doesn't block helpers.

[streamich]

LGTM.

[Dosant]

I removed matched because using regex as part of an API was a bad idea in a first place. If anyone would really want to have something like this this would be possible with extensions: #78404

Instead of match I added replace which allows to replace or remove a substring.

[elastic-jb]

Anton, the example I was thinking of was something like if I have a field that has "47.766201,-122.257057" stored as a single string field, it would be useful if I could have something that's kind of a cross between split and event.row so I could express that I want to use the value before the comma as a parameter, and the value after the comma as a separate parameter to send them to an API that requires them separately.

[elastic-jb]

Dropping match and adding replace makes sense. I think we have a good core here.

[Dosant]

@elasticmachine merge upstream

[Dosant]

Anton, the example I was thinking of was something like if I have a field that has "47.766201,-122.257057" stored as a single string field, it would be useful if I could have something that's kind of a cross between split and event.row so I could express that I want to use the value before the comma as a parameter, and the value after the comma as a separate parameter to send them to an API that requires them separately.

@elastic-jb, I added split 👍

[Dosant]

@elasticmachine merge upstream

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: ab17374

Metrics [docs]

page load bundle size

id	before	after	diff
uiActionsEnhanced	327.3KB	330.4KB	+3.0KB

History

• 💚 Build #82391 succeeded 2b14a9f
• 💚 Build #82373 succeeded c263117
• 💛 Build #82184 was flaky 4213b66
• 💚 Build #81585 succeeded 10c5017

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream