Anthony Reilly

Thanks for the contribution - I may have to modify it slightly to be compatible with another change I'm working on, but I'll get this integrated either way.

Currently, you would need to monitor for 4xx when the token or login session expires and then refresh the token. Adding an automatic token refresh is a priority for the...

Definitely sounds like it would be useful to handle the SF Date types more cleanly, and to avoid any accidental date shifts due to TZ.

Ill go ahead and take it for now, im going to look at a couple ways to integrate it into the client, I had been considering adding a couple new...

Generally, yes - it wraps the standard REST API : https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/intro_rest.htm While this doesn't implement all of the API, the usual CRUD type operations are supported. It's mainly meant for...

I think those things can be done via the Tooling API - https://developer.salesforce.com/docs/atlas.en-us.api_tooling.meta/api_tooling/intro_api_tooling.htm But I haven't added any of that functionality to this library. It's something I can look into...

Currently no direct replacement for DefaultContractResolver, may need custom implementation https://github.com/dotnet/runtime/issues/31257

Added a few things to 4.0.0-Beta to do this, some usage examples below: ``` SfContentVersion cv = await client.QuerySingle("SELECT Id,VersionData FROM ContentVersion WHERE ID = '0688W00000kkHmSQAU'"); SfContentVersion cv2 = await...

I'm adding partial support to begin with, to allow create/update/delete of multiple objects of the same type. I'll likely add the basic support for the more complex mixed composite requests,...

The SOAP api has a FieldsToNull property to address this, but I never found an equivalent in the REST api. Dropping the nulls was made the default behavior since that...