Issue with the documentation of create_preference

[ignaciolarranaga]

The create-preference payer.phone.number actually expects a number, not a string as said in the doc.
https://www.mercadopago.com.uy/developers/en/reference/preferences/_checkout_preferences/post

{
  "payer": {
    "phone": {
       "area_code": "",
       "number": 99123123,
    },
  },
}

Here is the change in the types: https://github.com/DefinitelyTyped/DefinitelyTyped/compare/master...ignaciolarranaga:DefinitelyTyped:payer-phone-fix?expand=1

[lucmantovani]

Hello @ignaciolarranaga!
Thank you for creating this discussion!

Just to clarify, where is the problem?
When executing through the SDK sending payer.phone.number as a string you get an error?
So the problem is that in the documentation it should be listed as numeric?

OBS: The DefinetlyTyped is not maintained by us, someone not from the company created it

[ignaciolarranaga]

Hey!, yep the issue is minor really. The doc says it expects a string, but if you send one string when calling the endpoint it says it must be a number.

https://www.mercadopago.com.uy/developers/en/docs/checkout-pro-v1/advanced-integration#bookmark_buyer's_personal_data:

Let's say the following throws an error:

import mp from 'mercadopago';

const payload = {
  payer: { ..., phone: { ..., number: "99123456" }, }
  ...
}
const response = await mp.preferences.create(payload);

The correct way is:

import mp from 'mercadopago';

const payload = { 
  payer: { ..., phone: { ..., number: 99123456 }, }
  ...
}
const response = await mp.preferences.create(payload);

CreatePreferencePayload from DefinetlyTyped is incorrect, but I guess it was based on the doc which also says string and it is not really the issue.

[lucmantovani]

Ok, thank you for reporting!
I will open an issue internally for a documentation fix