#well, the custom history_explorer card

1 messages · Page 1 of 1 (latest)

visual bronze
#

Yeah I see that history_explorer does a get_history API call for every entity in the system, which it uses to determine filtering.
Don't really think we'd want to duplicate that, sounds pretty heavy.
Probably better if core recorder would just expose this information somehow. Maybe in the future if recorder becomes more ui configurable, we'll get some of that information.

toxic delta
#

the HE card is very light n the system, and loads way faster than core History.... ive disabled it now, beause the dev stopped developing it, but it was a pleasure to work with

swift dove
#

I created an API for that

#

but we never merged it because we didn't have a use case for it in core

#

but should use json_bytes instead of JSON_DUMP now

#

@visual bronze If you want to use it, I'll dust it off and create a new PR

visual bronze
#

Sure I think that sounds good. If you provide the API, I think I can make a PR to use it.

#

I assume disabled recording applies equally to history and statistics?

swift dove
#

yes

toxic delta
#

Magic, you’re the best!

visual bronze
#

I do feel bad when I let people sneak FRs in where they don't belong 😂

toxic delta
#

Don’t…..

#

Sometimes it’s for the greater good