[Bug]: Phone inputs should expose dialcode in the formdata value automatically

[leonlazic]

Is there an existing issue for this?

• I have searched the existing issues

Description

I noticed this behaviour when I put a phone number input widget inside a Form widget. When I try to send with my query and the country code and the dial number I cannot append at the end .dialCode or .text.

I think this should work and I can just bypass the form reference altogether but it seems to me, like it would be better practice to reference anything in the form with Form.widget.specificvalue.

8e2332)

Steps To Reproduce

1. Put a phone number input into a form widget
2. Try to extract the dialCode or formatted number from the field by referencing the Form.data.inp_phone.text, Form.data.inp_phone.dialCode
3. It will not work

Public Sample App

No response

Environment

Production

Severity

Medium (Frustrating UX)

Issue video log

No response

Version

Cloud

[Nikhil-Nandagopal]

@leonlazic I think the right solution here would be to append the dial code to the start of the input in the form data field.
The form data field is meant to only contain the data entered by the user as a convenient way to send data to a query. So I'm against nesting an object of dial code and country code and other values inside it because it would defeat the purpose of the field and can be accessed from that widget directly.

[leonlazic]

I can understand you opinion. Appending the dial code at the start is an okay remedy for keeping everything referenced in the form data field simple.