-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PR #107 fixes character stripping allowed chars and adds tests ar… #108
Conversation
…ds tests around non-XML basket integration
That looks great :-) The only thing I would change is the parameter key "product_code" to lower camel-case "productCode". It's really minor, but is just a consistency thing with the rest of the package and other gateway drivers. |
Oh, also try merging in Also you have |
Hey @judgej - thank you! I've just refactored based upon the feedback you sent yesterday along with merging in master. Let me know if there is anything else I need to do 😄 . |
Just wondering, you'v used |
Hey @judgej, From the docs here https://www.sagepay.co.uk/file/12246/download-document/SERVER_Integration_and_Protocol_Guidelines_010814.pdf?token=zlCqBGKB7BlA503YTOOtRsBXWKcI4aVrqNSETHDIspk under |
@judgej - my bad, it is |
It talks about using the product codes to link the basket lines to the product records in Sage 50. It's not very clear, I know. |
There we go @judgej - hugely appreciate your time. |
Okay, merged in, with an additional to the extended item interface. Thank you. |
Hi @judgej , many thanks. |
Fixes stripping for
[]
which breaks theSage 50 Accounts Software Integration
. For more details please see #107 .The following work has been done:
XML integration
\Omnipay\SagePay\Message\AbstractRequest::filterNonXmlItemName
\Omnipay\SagePay\Extend\Item
with syntactical sugar for setting the product record for Sage 50 Accounts Software Integration as suggested by @judgej