AdHoc Filters: Allow custom value

[ashharrison90]

• allow specifying a custom value as the adhoc filter value
• adds a unit test to ensure we preserve this behaviour

Fixes grafana/grafana#85070

📦 Published PR as canary version: 4.3.0--canary.670.8538200720.0

✨ Test out this PR locally via:

npm install @grafana/scenes@4.3.0--canary.670.8538200720.0
# or 
yarn add @grafana/scenes@4.3.0--canary.670.8538200720.0

[dprokop]

Looks good. Question is if reloading the page with the custom value in URL will allow the value to be preserved? I think it's essential to make sure the custom value is persisted across reloads.

[ashharrison90]

Looks good. Question is if reloading the page with the custom value in URL will allow the value to be preserved? I think it's essential to make sure the custom value is persisted across reloads.

yep, reloading the page correctly restores the custom value 👍

[dprokop]

Works well for Prometheus :)

I wonder - is there any way in the Select that would allow us to edit the manually entered filter value? I think it would be very helpful for scenarios when one makes a type.

[ashharrison90]

@dprokop i don't think there's a prop on the component that would let us do that. i know exactly what you mean, that could get annoying. i'm sure we were discussing this in frontend platform the other day. i'll do some searching

[grafanabot]

🚀 PR was released in v4.3.0 🚀