Fixed custom fields with null value

The custom fields with null value were giving the custom field key itself as a value instead, it's fixed now and it returns null as it should.

(Due to automation issues, the changes are available in this version, but the changelog entry is available on v17.5.1.)

Renamed file with long name

• Renamed file with long name and it's class, so the SDK can be installed via yarn.

Old name:
AnyOfRecentsActivityRecentsActivityTypeRecentsDealRecentsFileRecentsFilterRecentsNoteRecentsPersonRecentsOrganizationRecentsPipelineRecentsProductRecentsStageRecentsUser

New name:
AnyOfRecents

Fixed PUT /persons/{id}

• Updated PUT /persons/{id}: parameter name is not required while updating a person.

OpenAPI Generator beta version of the Pipedrive SDK

With this version we'll move to an open-source SDK generator. This release includes all of the previous features plus additional IDE support. We'll be actively developing this and will hopefully get this out of beta in the future. This version includes all of the lates API endpoints.
If you have any suggestions or feedback we would be happy to hear from you through Github issues.

v10.0.0 Add async/await support, OAuth improvements and more

Version 10 is a complete rewrite of the library and introduces breaking changes in the client API. This release includes improved OAuth 2 support, async & await / promises and access to all Pipedrive API endpoints.

v9.2.0 OAuth 2.0 Bearer token support

This release adds support for using OAuth 2.0 access tokens for authorization

v9.1.1

Minor cleanup and integration test tweaks.

v9.1.0

This release includes a change in how multipart uploads to Pipedrive API are handled.

Fixes #50

v9.0.0 Dropped support for Node 6, added inflection to dependencies

• Node versions 8, 10, 12 are now supported
• Moved inflection.js from hardcoded file to npm dependencies

v8.0.0 Dropping of client.on() feature

Pipedrive CORE tribe that supports websocket connectivity wants to have performant UI of tha app, but having library's integrations connecting to socketqueue service on channelx.pipedrive.com is affecting its stability. It is also another dependency that we would like to avoid whenever we change authentication mechanisms and for future plans to improve scalability of our architecture.

Thats why we need to drop the beta feature of .on() event subscription

We suggest you use webhooks for event delivery that can be predictably scaled & limited by our infrastructure