You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Really handy library !. Have been battling for a couple of hours with something so putting a note here.
The types for PropertyType are spot on for the enums - however Zoopla also support a string ontop of the enum list.
From the ZPG spec If you believe that there is a significant difference between your property type and those that we support, then send your property type as a readable string. In such cases we will display property type as "Property"
I've been attempting to send a property without using an enum and do not think this library allows for it.
To get around this I ended up creating a new propertyType of Property => property just to be able to send it. This then fails validation on the validation routine, so I've ended up adding a final parameter to sendProperty(param1,2,3 etc, .. $skip_validation) which (temporarily to get around this) lets me skip the validation.
Any thoughts on how to include this somewhat lax feature in the spec in a better way ?
Thanks again.
The text was updated successfully, but these errors were encountered:
Really handy library !. Have been battling for a couple of hours with something so putting a note here.
The types for PropertyType are spot on for the enums - however Zoopla also support a string ontop of the enum list.
From the ZPG spec If you believe that there is a significant difference between your property type and those that we support, then send your property type as a readable string. In such cases we will display property type as "Property"
I've been attempting to send a property without using an enum and do not think this library allows for it.
To get around this I ended up creating a new propertyType of Property => property just to be able to send it. This then fails validation on the validation routine, so I've ended up adding a final parameter to sendProperty(param1,2,3 etc, .. $skip_validation) which (temporarily to get around this) lets me skip the validation.
Any thoughts on how to include this somewhat lax feature in the spec in a better way ?
Thanks again.
The text was updated successfully, but these errors were encountered: