I'm using this library to automate my vultr projects but there's no version number association so I'm unable to isolate a specific revision with composer. Also, because I did some bug-fixes/touch-ups, I wanted to create a patch file for the current revision. When do you think we can see a version 0.0.1 or 1.0.0?

I have many reasons for this request.

1. Stable distributions ( production environments ) haven't fully adopted php8.
2. The latest Ubuntu release defaults to php7 ( in my case php8 was a headache to get working )
3. Not all modules have or are php8 friendly, I had to use custom/questionable repos and still failed due to a buggy module.

The only way I can run this library is through a docker image. Perhaps other people are experiencing similar issues.

The createFirewallRule function is missing in src/Services/Firewall/FirewallService.php file. After implementing it, I had trouble setting a subnet to 0.0.0.0/0 because getInitializedProps() routine wouldn't return properties with a value of 0.

I ended up writing this to get what I needed working.

• public function createFirewallRule(string $group_id, FirewallRule $rule) : FirewallRule
• {

•  $properties = $rule->getInitializedProps();
  

•  if ( !isset( $properties['subnet_size'] ) )
  

•      $properties['subnet_size'] = 0;
  

•  return $this->createObject('firewalls/'.$group_id.'/rules', new FirewallRule(), $properties);
  

• }

Description

Adds PHPDoc property typehints on the VultrClient class. This doesn't affect any behavior but helps the IDE typehint what properties are available.

As a side note - if you required ^8.1 instead of ^8.0 you could use public readonly properties to accomplish the task a little cleaner/more type-safe (4ac77f8ff8f3ac78b280c53f6c33535104a10c56 - although not proposing this now as readonly properties were only added in 8.1)

Checklist:

• [X] Have you checked to ensure there aren't other open Pull Requests for the same update/change?
• [X] Have you linted your code locally prior to submission?
• [X] Have you successfully ran tests with your changes locally?

The api crashes with an invalid request error when ever I try to create a firewall rule set to accept from anywhere ( 0.0.0.0/0 ). I brought this up as a side note before that getInitializedProps wont return key pairs when the value evaluates to false. I tested this on the latest version 0.2.3.

The namespace declaration for ListOptions is missing from /src/Services/VPC/VPCService.php and /src/Services/Firewall/FirewallService.php files which causes the library to crash when calling list methods.

This can be reproduced by calling $client->firewall->getFirewallGroups and $client->vpc->getVPCs

Checklist:

• [x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?
• [x] Have you linted your code locally prior to submission?
• [x] Have you successfully ran tests with your changes locally?

Description

Add phpdoc generation and additional comments

Checklist:

• [x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?
• [x] Have you linted your code locally prior to submission?
• [x] Have you successfully ran tests with your changes locally?

Checklist:

• [x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?
• [x] Have you linted your code locally prior to submission?
• [x] Have you successfully ran tests with your changes locally?

Is your feature request related to a problem? Please describe. The need to alleviate long exception messages when, I can just view previous exceptions for more additional information if needed.

Describe the solution you'd like To stop the chaining of try/catches in many functions throughout the service handlers

Example: