Proper date and timezone in the VIES response

Where we used to have an issue with the time always being set to 02:00 was in fact the timezone the request was made and not the time. As was researched by @cottton, the VIES service returns only the date and the timezone where the request was made for.

So now this VIES service will return you the correct date and the correct timezone, but as the time itself is not returned, it will default to "00:00:00".

Kudos to @cottton for raising the issue and fixing the problem. 🏅

Validating non-numeric input for numeric VAT ID's

In issue #67 reported by @willemstuursma wrong input validation failed. This is fixed now in the latest release of VIES 2.1.7.

Quick fix for Bulgarian VAT ID's

There was an issue validating VAT ID's for natural persons in Bulgaria, which this version fixes. Thanks to @mato61 for reporting it in issue #34.

December updates

This release has some interesting updates:

• Update of sensiolabs/security-checker by @arjank
• Extra test for the undefined SOAP_1_2 constant warning (issue #60) reported by @gasperkol
• Adding Docker containers to make testing a whole lot easier (documentation will follow soon)
• Removal of dead code

Many thanks to all for helping me improve this package. I wish all of you happy holidays and a wonderful 2019!

Michelangelo

Intermediate update

This update contains no logic enhancements, only a few more examples to play with and an update of the README.md to explain the unexpected things that we have in our library like the EL prefix for Greek VAT ID's.

Intermediate bug fix release for Slovenian VAT ID's

This fixes Issue #54 for Slovenian VAT ID's

Back porting fix for Slovenian VAT ID's

This fixes Issue #54 for Slovenian VAT ID's

Trader check by VIES

In PR #51 @Freeaqingme requested for a trader check by the VIES service but for some reason his contribution kept failing our unit tests.

So taking his suggestion to heart, I've build and implemented the basic functionality to perform VIES service-side checking of the additional information you pass along the request for validation.

I've also improved the code coverage to cover 100% of the code base and updated the README to better explain the functionality and the possibilities of the service.

I want to thank all that have suggested improvements on the code to make this tool a valuable part of your business workflow.

Updates of software packages and GDPR

This is a small update:

We have just updated dependent composer packages
We have added a GDPR statement in the README

Updates of software packages and GDPR

This is a small update:

• We have just updated dependent composer packages
• We have added a GDPR statement in the README