eval loading state should be true as soon as it's data method is called

[ShiboSoftwareDev]

current behavior is that the loader starts spinning only when the task method for that eval is called, so when the data step takes too long you will not see immediate feedback and it's confusing

[mattpocock]

This is non-trivial, and cosmetic, so will likely not push for this soon. The best way to mitigate this is to make the data functions resolve quickly. You shouldn't be doing LLM calls inside data, since traces won't be captured.

But - I agree that it should work in the way described.