I wonder if this issue points to our needing another layer in the API to make such indicator behaviour consistent?
I wonder if this issue points to our needing another layer in the API to make such indicator behaviour consistent?