nbfontana / ngx-br Goto Github PK

Expected Behavior

<cpfCnpj ....> to format/parse acording to input value.

Actual Behavior

None

Telefone component should mask both, residential phone numbers and cell phone numbers

Expected Behavior

<cpf .... required></cpf> inject 'required' into <input cpfMask....

BTW, this could be the default behavior of any attribute, by-pass them to component.

Actual Behavior

It ignores the 'required' attribute.

Expected Behavior

Estava pensando em incluir o módulo de cálculo de aposentadoria no ngx-br.

Actual Behavior

Pensei em perguntar se há ou não necessidade disso, do que fazer um código e ele ser rejeitado.

Steps to Reproduce the Problem

1. Existem aposentadoria atual que é o tempo de idade e o tempo de serviço, isso geralmente é para funcionário público
2. existem outros tipos de aposentadoria(que vai além de ser funcionário público), como a aposentadoria para alguma classe política

Specifications

• Version: última versão
• Platform: debian
• Subsystem: linux

Feel free to give some Ideas for the project!

Expected Behavior

The model value has the unformatted field value, but on error handling the formatted value typed could be used in user feedbacks, i.e. 'O CPF '000.111.222-33' é inválido.'

Actual Behavior

Could not find the formatted value on formcontrol. I´ll have to use vanilla to format my customized error or use some sort of feature to recover ElementRef to get nativeValue, with this 'feature' it would not be required.

Today we have a Telefone component that handles both, cell phone and fixed phone number, but we should have a simple one only with a fixed phone mask.

The feature should include a pipe and a mask as well.

Suggested changes

The input cpf, cnpj, tel and cep change to type = "tel".

Improves typing on mobile

Today we have a Telefone component that handles both, cell phone and fixed phone number, but we should have a simple one only with a cell phone mask.

The feature should include a pipe and a mask as well.