Better/strict typehinting?

[JanMikes]

Hello there!

I just started using this library - everything works as expected, thought i have a bit pain with typehinting methods, so my IDE understands return types, like this:

As you can see from screenshot, it is not good programmer experience in code like that.

Is there any chance, this will get improved?

[JanMikes]

One more hint, using magic methods like this makes package almost impossible to test with static analysis, etc phpstan - http://github.com/phpstan/phpstan which can prevent many bugs in code

[IsraelOrtuno]

I understand what you say, but tried to use DRY pattern in order to simplify the development and maintenance... Would be open to merge a PR with all resources with their methods tho..

[JanMikes]

Hi @IsraelOrtuno and what about adding @method annotations? like this:

/**
 * @method Activities activities()
 * @method ActivityFields activityFields()
 *  ..... and more
 */
class Pipedrive

It will allow IDE to autocomplete and better understand the code:

Mind if i prepare PR like this? 😉

[JanMikes]

Will be very happy for merging and tagging a version for composer 🌹