Url state

[stephmilovic]

Uses url parameters to store timerange and kql data. Also tracks whether the timerange is locked or not

I have a couple more tests to write but wanted to get the PR up.

Happy path manual tests:

• change the datepicker
• check that the url has updated
• refresh the page, ensure that timerange remains
• add a kql query
• check that the url has updated
• refresh the page, ensure that kql query remains

[elasticmachine]

💔 Build Failed

• continuous-integration/kibana-ci/pull-request

[elasticmachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request

[elasticmachine]

Pinging @elastic/secops

[elasticmachine]

💔 Build Failed

• continuous-integration/kibana-ci/pull-request

[elasticmachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request

[angorayc]

Thanks for taking care of this @stephmilovic! I followed the past above but found that the status for date-picker persisted well, but my kql query is unable to remain after refreshing page. Please let me know if you can reproduce it.

[stephmilovic]

@angorayc thanks for reviewing. Can you please post the full url? it might be because the kql query does not persist between pages, only on the page it was set

[angorayc]

This is what I've got, seems that kql is not a part of it. Hope it helps

http://localhost:5601/app/siem#/hosts?_g=()&timerange=(global:(from:1558195200000,fromStr:now%2Fw,kind:relative,linkTo:!(timeline),to:1558799999999,toStr:now%2Fw),timeline:(from:1558195200000,fromStr:now%2Fw,kind:relative,linkTo:!(global),to:1558799999999,toStr:now%2Fw))

[XavierM]

I think we should have an empty state URL on initialization. So an user can still share their URL and show what they saw at this time

[XavierM]

@angorayc I think that you found a usability bug, we should link the refresh button to apply the KQL search in the KQL bar.

[stephmilovic]

There are 2 remaining ts issues, this is one of them. I've spent the better part of the past 6 hours trying to figure this out. May need to merge and come back. Even after adding UrlStateMappedToActionsType and wrapping it in another if, it still gives this error:

[stephmilovic]

There are 2 remaining ts issues, this is one of them. I've spent the better part of the past 6 hours trying to figure this out. May need to merge and come back. Both @spong and @XavierM have spent time pairing on this, it's a toughy:

[XavierM]

LGTM, and please create issues so we can track these problems

[stephmilovic]

Opened this issue for the remaining work: https://github.com/elastic/ingest-dev/issues/447