You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am having an issue. When I try to navigate back in time in the ruby browser we have so many events that each pagination click represents 1-2 minutes of events, which makes it impossible to look back 1 week for example. Would it be possible to add some filtering on the created_at attribute.
Also when I look at an event and then navigate back to the index page it always starts on page 1, instead of the page i was on before i clicked on an event :)
I don't now Elm, otherwise I would try to create a PR myself
Thanks
The text was updated successfully, but these errors were encountered:
Would it be possible to add some filtering on the created_at attribute
Filtering on timestamps needed some groundwork and it has been just recently done: #674. Let's say it is scheduled for 2.0 release.
There was also an earlier PR which adressed an API for filtering #593 and that can be brought back to life now.
With an API for filtering present on Client facade we can finally think about adding time filtering to UI
Also when I look at an event and then navigate back to the index page it always starts on page 1, instead of the page i was on before i clicked on an event :)
I think @swistak35 was on it in #727 or at least we discussed improving this very thing
Hi guys
I am having an issue. When I try to navigate back in time in the ruby browser we have so many events that each pagination click represents 1-2 minutes of events, which makes it impossible to look back 1 week for example. Would it be possible to add some filtering on the created_at attribute.
Also when I look at an event and then navigate back to the index page it always starts on page 1, instead of the page i was on before i clicked on an event :)
I don't now Elm, otherwise I would try to create a PR myself
Thanks
The text was updated successfully, but these errors were encountered: