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
In Magento1 vsBridge, json response is created using json_encode with JSON_NUMERIC_CHECK flag.
I guess it's to have all ids in an integer format.
But, it creates some unexpected behaviors:
cartId: Magento1 (contrary to Magento2), has integer values for cartId. but src/models/order.schema.json from vuestorefront-api defines it as string. Therefore, the schema cannot be validated
Shipping addresses: postcode and telephone are converted to integer but again, the schema requires them as strings
It's possible to have same bugs elsewhere in magento1 vsBridge (i didn't tested everything)
The text was updated successfully, but these errors were encountered:
In Magento1 vsBridge, json response is created using
json_encode
withJSON_NUMERIC_CHECK
flag.I guess it's to have all ids in an integer format.
But, it creates some unexpected behaviors:
cartId
. butsrc/models/order.schema.json
fromvuestorefront-api
defines it as string. Therefore, the schema cannot be validatedpostcode
andtelephone
are converted to integer but again, the schema requires them as stringsIt's possible to have same bugs elsewhere in magento1 vsBridge (i didn't tested everything)
The text was updated successfully, but these errors were encountered: