Solucionado (ver solução)
Solucionado
(ver solução)
1
resposta

Está estorando um monte de erro no console por causa do ErrorHandler :/

Alguém sabe o pq?

_co.signupForm.get(...).errors.email is not a function
global-error-handler.ts:44 Object.eval [as updateDirectives] (ng:///HomeModule/SignupComponent.ngfactory.js:354:110)
debugUpdateDirectives (webpack:///node_modules/@angular/core/fesm5/core.js:11054:)
checkAndUpdateView (webpack:///node_modules/@angular/core/fesm5/core.js:10451:)
execProjectedViewsAction (webpack:///node_modules/@angular/core/fesm5/core.js:10692:)
execComponentViewsAction (webpack:///node_modules/@angular/core/fesm5/core.js:10634:)
checkAndUpdateView (webpack:///node_modules/@angular/core/fesm5/core.js:10457:)
execProjectedViewsAction (webpack:///node_modules/@angular/core/fesm5/core.js:10692:)
asElementData (webpack:///node_modules/@angular/core/fesm5/core.js:10655:)
checkAndUpdateView (webpack:///node_modules/@angular/core/fesm5/core.js:10452:)
execProjectedViewsAction (webpack:///node_modules/@angular/core/fesm5/core.js:10692:)
global-error-handler.ts:45 o que será enviado para o serviço
global-error-handler.ts:54 DOMException: Failed to execute 'open' on 'XMLHttpRequest': Invalid URL
    at http://localhost:4200/polyfills.js:15167:31
    at XMLHttpRequest.proto.<computed> [as open] (http://localhost:4200/polyfills.js:13478:24)
    at Observable._subscribe (http://localhost:4200/vendor.js:7374:17)
    at Observable.push../node_modules/rxjs/_esm5/internal/Observable.js.Observable.subscribe (http://localhost:4200/vendor.js:67291:69)
    at DoOperator.push../node_modules/rxjs/_esm5/internal/operators/tap.js.DoOperator.call (http://localhost:4

html

<ap-vmessage
          *ngIf="signupForm.get('email').errors?.required && (form.submitted && signupForm.get('email').touched)"
          text="email is required!">
        </ap-vmessage>
        <ap-vmessage
          *ngIf="signupForm.get('email').errors?.email (form.submitted && signupForm.get('email').touched)"
          text="invalid email!">
        </ap-vmessage>
1 resposta
solução!

ignorem, ja foi resolvido rs