I'm opening this topic to hear from you how you've been working on the issue of adding RG to forms.
I think a common concern of everyone when working with forms is that data control is in our hands - not the user's hand.
For this, the better formatted and controlled each field, the better.
One of my big problems is how to control the RG field.
That's why - and for most of the clients I work with, the RG is unnecessary - I somehow convince the client to "ignore" the field in their forms, but now I'm having to work with the RG that is required for a client.
As I do not have a lot of experience, I would like to know how you have worked with RG - whether you are leaving the field open, controlling or controlling in any way.
From what I saw, read, re-read, the best way to control the field is to lock it to only digits - and format it as XXX.XXX.XXX-X - and inform the user that if the digit is " X "(which is why I replace the 10 in the digit) replace with ZERO.
I do not know if this is the best way to do it - and if it will cover 100% of the reality of the RGs .. (the only letter we have in the RG is X in the digit?)
My need is not a VERIFIER - because this is impossible - but only a MASK control - to avoid completely random data and leave the field as standardized as possible.
The important thing is that the mask is 100% compatible with all types of RGs.