npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@schaman/angular-material-error

v3.0.1

Published

Adding every form error in your application is boilerplate.

Downloads

246

Readme

@schaman/angular-material-error

Adding every form error in your application is boilerplate.

Setup

Import the SchamanMaterialErrorModule.

Provide your own ErrorMessageProvider to use your own messages. Pro-tip: inject other translator services.

@Injectable()
export class MyFancyErrorMessageProvider extends ErrorMessageProvider {
  public constructor(private readonly translateService: TranslateService) {
    super();
  }
  public getErrorMessagesFor(errors: ValidationErrors): string {
    if (errors.required) {
      return this.translateService.get('ERROR.REQUIRED');
    }
    if (errors.pattern) {
      if (errors.requiredPattern === emailPattern) {
        return this.translateService.get('ERROR.EMAIL_PATTERN');
      }
      return this.translateService.get('ERROR.UNKNOWN_PATTERN');
    }
    return this.translateService.get('ERROR.UNKNOWN');
  }
}
@NgModule({
  providers: [
    {
      provide: ErrorMessageProvider,
      useClass: MyFancyErrorMessageProvider,
    },
  ],
})
export class Module {}

In your component use the *schamanDynamicError directive:

@Component({
  template: `<mat-form-field>
    <input matInput [formControl]="formControl" />
    <mat-error *schamanDynamicError></mat-error>
  </mat-form-field>`,
})
class DirectiveTestComponent {
  formControl = new FormControl('', Validators.required);
}

This will add and remove the error text if needed. (On state change or form submit.)

Overrides

You can also add a custom ErrorMessageProvider on component level to override the translations in a single component.

@Component({
  /* ... */
  providers: [
    {
      provide: ErrorMessageProvider,
      useClass: MyFancierErrorMessageProvider,
    },
  ],
})
export class FancierComponent {}

Running unit tests

Run nx test angular-material-error to execute the unit tests.