In TA, we've implemented our own little custom hook policy that diverges from other services. This wasn't the best idea, since the custom hook policies are supposed to be consistent across services (they should really just returns the raw pipeline response).
Now that we're adding the multiple actions endpoint, we're running into some questions about what we should do here: should we add support for this for the multiple actions endpoint? we also have multiple statistics now (for single action endpoint, statistics is singular, while there will be statistics for every action inputted in the multiple actions endpoint
In TA, we've implemented our own little custom hook policy that diverges from other services. This wasn't the best idea, since the custom hook policies are supposed to be consistent across services (they should really just returns the raw pipeline response).
Now that we're adding the multiple actions endpoint, we're running into some questions about what we should do here: should we add support for this for the multiple actions endpoint? we also have multiple statistics now (for single action endpoint,
statisticsis singular, while there will be statistics for every action inputted in the multiple actions endpoint