* 8.x-3.x:
  Issue #2838449 by aaronbauman - Updates to Mapped Object revisioning - update hook_field_extra_fields() - ditch function salesforce_mapping_get_fieldmap_types()

Conflicts:
	modules/salesforce_mapping/src/Entity/MappedObject.php
	modules/salesforce_mapping/src/Form/MappedObjectForm.php

- update hook_field_extra_fields()
- ditch function salesforce_mapping_get_fieldmap_types()

- Add Describe response class
- Drop Upsert response class (upsert returns an SFID)
- add __get to base response class and simplify child classes

* 8.x-3.x: (22 commits)
  Couple more changes to adding fields UI. CSS is still garbage, but the new mechanism is working now.
  undefined variable in basefielddefinitions
  by aaronbauman - prevent exception within catch()
  checking off more todos!
  by aaronbauman - remove salesforce_mapping_entity_delete in order to preserve historic record of mappings. This can be useful for data forensics. - final tweaks on push before merging upstream
  Fixes method call in SalesforcePushEvent constructor
  entity and mapping on Push Event
  by aaronbauman - refine PushParams class and events
  Check off that todo
  by aaronbauman - get rid of SOAP-specific fieldsToNull
  Add REST version of SalesforceMapping::getPushParams
  Fixes namespacing errors
  Fixes a lot of syntax errors
  by aaronbauman - more events
  .
  by aaronbauman - initial pass at Events framework. Add event "PushParams"
  by aaronbauman - handful of style tweaks and updates to Constant and Token properties
  by aaronbauman - refactor field mappings to make plugins more pluggable - "validate" delegation - "submit" delegation - all mapping fields are delegated to field plugin system - get rid of tables on field mapping layout - continue thinning out SalesforceMappingFieldsForm controller
  exception handling for pull / mapping loads, etc. ANOTHER BROKEN COMMIT - NEEDS TO BE FIXED STILL
  Walking through field mapping pull loop intent w Rhodes. This commit will probably break things.
  ...

Conflicts:
	modules/salesforce_mapping/src/Entity/MappedObject.php
	modules/salesforce_push/salesforce_push.module
	src/Rest/RestClient.php

Field mapping ui

Couple more changes to adding fields UI. CSS is still garbage, but the new mechanism is working now.

* 8.x-3.x:
  by aaronbauman - prevent exception within catch()

* 8.x-3.x:
  checking off more todos!
  by aaronbauman - remove salesforce_mapping_entity_delete in order to preserve historic record of mappings. This can be useful for data forensics. - final tweaks on push before merging upstream
  Fixes method call in SalesforcePushEvent constructor
  entity and mapping on Push Event
  by aaronbauman - refine PushParams class and events
  Check off that todo
  by aaronbauman - get rid of SOAP-specific fieldsToNull
  Add REST version of SalesforceMapping::getPushParams
  Fixes namespacing errors
  Fixes a lot of syntax errors
  by aaronbauman - more events
  .
  by aaronbauman - initial pass at Events framework. Add event "PushParams"

- remove salesforce_mapping_entity_delete in order to preserve historic record of mappings. This can be useful for data forensics.
- final tweaks on push before merging upstream

by aaronbauman - Standardize responses across some key REST endpoints and start working towards a framework for better extensibility in the REST layer.

Fixes parameter order in PushParams instantiation in MappoedObject
Removes explicit language arrays in MappedObject instantiation in
salesforce_push.module. (The MappedObject constructor already takes
care of that already.)

# By git
# Via git
* 'events-framework' of bitbucket.org:messageagency/sf:
  Add REST version of SalesforceMapping::getPushParams

Conflicts:
	modules/salesforce_mapping/src/Entity/SalesforceMapping.php

* 8.x-3.x:
  by aaronbauman - - Introduce RestException and RestResponse for RestClient interactions - Add revisioning for Mapped Object - Re-introduce last_sync_status and last_sync_action
  by aaronbauman - adds revisioning to mapping objects by implementing RevisionableContentEntityBase interface

Conflicts:
	modules/salesforce_mapping/src/Entity/MappedObject.php
	modules/salesforce_mapping/src/Entity/SalesforceMapping.php

* 8.x-3.x:
  by aaronbauman - - Introduce RestException and RestResponse for RestClient interactions - Add revisioning for Mapped Object - Re-introduce last_sync_status and last_sync_action
  by aaronbauman - adds revisioning to mapping objects by implementing RevisionableContentEntityBase interface

Conflicts:
	modules/salesforce_mapping/src/Entity/MappedObject.php
	modules/salesforce_push/salesforce_push.module

- Introduce RestException and RestResponse for RestClient interactions
- Add revisioning for Mapped Object
- Re-introduce last_sync_status and last_sync_action

Fixes type mismatch errors in RestClient use in MappedObject:push

- functions needed ‘function’ keyword
-  fixes PushParams use declaration in SalesforceMapping

by aaronbauman - adds revisioning to mapping objects by implementing RevisionableContentEntityBase interface

* 8.x-3.x:
  by aaronbauman - update hook_entity operations for salesforce_push for D8 Since push operations are handled inside MappedObject, we don't need all this logic inside salesforce_push. My general goal here is to get real-time REST operations up and running, then move on to queue/batch operations, and leverage SOAP where appropriate. End users shouldn't have to decide whether to use REST or SOAP or even know the difference. Drupal should use them as appropriate, given admin settings. To that end, salesforce_push_cron is still just a stub and hasn't been touched. MappedObject is way too fat, and will probably be slimmed down in the future - especially push() and pull(), which belong somewhere else.

Conflicts:
	modules/salesforce_mapping/src/Entity/SalesforceMapping.php

* 8.x-3.x:
  by aaronbauman - update hook_entity operations for salesforce_push for D8 Since push operations are handled inside MappedObject, we don't need all this logic inside salesforce_push. My general goal here is to get real-time REST operations up and running, then move on to queue/batch operations, and leverage SOAP where appropriate. End users shouldn't have to decide whether to use REST or SOAP or even know the difference. Drupal should use them as appropriate, given admin settings. To that end, salesforce_push_cron is still just a stub and hasn't been touched. MappedObject is way too fat, and will probably be slimmed down in the future - especially push() and pull(), which belong somewhere else.

Conflicts:
	modules/salesforce_push/salesforce_push.module

Since push operations are handled inside MappedObject, we don't need all this logic inside salesforce_push. My general goal here is to get real-time REST operations up and running, then move on to queue/batch operations, and leverage SOAP where appropriate. End users shouldn't have to decide whether to use REST or SOAP or even know the difference. Drupal should use them as appropriate, given admin settings. To that end, salesforce_push_cron is still just a stub and hasn't been touched. MappedObject is way too fat, and will probably be slimmed down in the future - especially push() and pull(), which belong somewhere else.

* 8.x-3.x:
  by aaronbauman - Add method chaining to RestClient when possible
  Fix overwriting refresh token on re-auth
  Alpha sort the entity type options.
  Don't let date trigger field validation block necessary form AJAX.
  Clean up unused code.
  Clean up use statements in CRUD form.
  Refactor get_salesforce_object() to tolerate empty values.

* 8.x-3.x:
  by aaronbauman - Add method chaining to RestClient when possible
  Fix overwriting refresh token on re-auth
  Alpha sort the entity type options.
  Don't let date trigger field validation block necessary form AJAX.
  Clean up unused code.
  Clean up use statements in CRUD form.
  Refactor get_salesforce_object() to tolerate empty values.

Conflicts:
	modules/salesforce_mapping/src/Form/SalesforceMappingFieldsForm.php
	modules/salesforce_mapping/src/Form/SalesforceMappingFormCrudBase.php