You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there any thought around separating out the Plaid request/response models from the HttpClient logic?
I'm working in a project which needs to parse and manipulate Plaid data, but not download that data from Plaid directly. It would be nice to have access to the C# classes for deserializing JSON without pulling in all of Going.Plaid which depends a bunch of other stuff like Microsoft.Extensions.Http. What about a Going.Plaid.Abstractions package with as few dependencies as possible, which the main Going.Plaid package could depend on?
The text was updated successfully, but these errors were encountered:
Is there any thought around separating out the Plaid request/response models from the HttpClient logic?
I'm working in a project which needs to parse and manipulate Plaid data, but not download that data from Plaid directly. It would be nice to have access to the C# classes for deserializing JSON without pulling in all of Going.Plaid which depends a bunch of other stuff like Microsoft.Extensions.Http. What about a
Going.Plaid.Abstractions
package with as few dependencies as possible, which the mainGoing.Plaid
package could depend on?The text was updated successfully, but these errors were encountered: