When I first wrote Site.GetTokensAsync, I had assumed that a user might want to retrieve different tokens in one MW API request. But this assumption led to too much complexity. On the other hand, its overload in singular form GetTokenAsync is used much more often compared with GetTokensAsync.
To reduce the complexity and make it easier to maintain, I'm going to remove GetTokensAsync. If, in the rare case, I assume, you want to retrieve multiple tokens, you will need to call GetTokenAsync multiple times.
When I first wrote
Site.GetTokensAsync
, I had assumed that a user might want to retrieve different tokens in one MW API request. But this assumption led to too much complexity. On the other hand, its overload in singular formGetTokenAsync
is used much more often compared withGetTokensAsync
.To reduce the complexity and make it easier to maintain, I'm going to remove
GetTokensAsync
. If, in the rare case, I assume, you want to retrieve multiple tokens, you will need to callGetTokenAsync
multiple times.