Version X - Encoding improvements

[veewee]

Feature Request

The most known issues happen at ext-soap encoding / decoding's.
Again, because these are limitations in PHP's SOAP implementation, it is not something we can deal with at this time.
In order to solve this, we would need to write a pure PHP encoding / decoding implementation - which is a lot of work.

In this issue, we'll list the known issues:

Summary

• Lack of support for namespaced (duplicate) type-names
•  Type converters
  • Lack of built-in support for [encoding / decoding enums](https://github.com/phpro/soap-client/blob/master/docs/
    known-issues/ext-soap.md#enumerations)
  • Unkown element context when converting to xml from inside a typemap (DateTimeTypeConverter is changing attribute name. How to prevent? #501)
  • Make it possible to provide a type converter for the any xsd type (Injecting AnyType converter into soap response php-soap/ext-soap-engine#17)
• A property with a hyphen or other non-accepted property character in the name (A property with a hyphen in the name #477)
• An easier way to deal with CDATA
  • (How to force CDATA for a specific SOAP Element? php-soap/ext-soap-engine#19)
• Improve support for special array types like soapenc:array, apache:map, ... See:
  • (unsignedInt type not supported #504 (comment) and unsignedInt type not supported #504 (comment))
• hydrate nested inherited private props (Typed property ... must not be accessed before initialization #513)
• Validate that nullable response types dont result in an unitialized property issue (Set null as a default value for nullable properties #515)

Requested BC breaks

•  Code generation improvements
• Allow getters/Setters with underscores (Two properties (one with an underscore _ one without) results in having only one getter method #502)

...

Timeframe

Development happens when it happens...
By sponsoring the project, we can inject some more time into this project.

Find out how you can help out 💚