Missing 'limit' and 'offset' parameters

[Jericho]

In the process of implementing the changes for #361 and #367, it occurred to me that some methods don't support the 'limit' and 'offset' parameters which are necessary for paging. This seems to have been added to the SendGrid API some time ago but there was no announcement or mention of this in SendGrid's release notes. This explains why some methods in the StrongGrid library, such as ApiKeys.GetAllAsync for example, currently do not support paging.

I will update the following list of methods that are missing the 'limit' and 'offset' parameters:

• Apikeys.GetAllAsync. SendGrid's documentation talks about the limit parameter but not the offset. That's very odd and I am assuming it's simply an error in the documentation.
• IpAddresses.GetUnassignedAsync This one is more complicated that it seems at first glance. Simply adding 'limit' and 'offset' does not completely solve the paging issue because we invoke GellAllAsync and filter the result in order to find 'unassigned' addresses. This means that page number 2 of unassigned addresses does not necessarily correspond to page number 2 of all addresses. I need to think about how I will resolve this issue.
• Teammates.GetAllPendingInvitationsAsync. SendGrid's documentation does not address whether this endpoint supports 'limit' and 'offset' but I performed some testing and I did not observe any error when specifying these two parameters. Therefore I will assume this endpoint does indeed support 'limit' and 'offset'.
• AccessManagement.GetAccessHistoryAsync . This is another case where SendGrid's documentation talks about the limit parameter but not the offset. Again, I'm assuming it's simply an error in the documentation. UPDATE January 2022: SendGrid throws "unknown field" exception when adding "offset" to the request
• EmailActivities.SearchAsync. Another case where SendGrid's documentation talks about the limit parameter but not the offset. UPDATE January 2022: I am not able to test this change because my account is not signed up for the Email Activities API. Therefore I am not going to make any change to this functionality.

[Jericho]

I'm having second thoughts about adding limit and offset to the IpAddresses.GetUnassignedAsync method because GetAssignedAsync does not allow limit/offset and I think it makes sense for the signature of these two methods to be consistent.

[Jericho]

Adding offset to the request when invoking AccessManagement.GetAccessHistoryAsync caused the following error:

{
    "errors": [
        {
            "field":"offset",
            "message":"unknown field"
        }
    ]
}

Therefore, I will not be adding offset to this method.

[Jericho]

🎉 This issue has been resolved in version 0.85.0 🎉

The release is available on:

• GitHub Release
• NuGet Package

Your GitReleaseManager bot 📦🚀