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

@sungazer/nebular-validation-errors

v13.0.0

Published

This package automatically shows validation errors in forms built with Nebular [https://akveo.github.io/nebular/](https://akveo.github.io/nebular/)

Downloads

33

Readme

NebularValidationErrors

This package automatically shows validation errors in forms built with Nebular https://akveo.github.io/nebular/

It comes with a configurable error normalizer that allows to configure what is shown in the error tooltip.

Example

See here: https://sungazer-pub.gitlab.io/nebular-validation-errors

Usage

Import the NbErrorTooltipModule in the module where you want to use the nbErrorTooltip directive.

Apply the nbErrorTooltip directive to nbInput components and add some validation requirements to the element.

<input [(ngModel)]="formData.field3" minlength="3" name="field3" 
nbErrorTooltip nbInput placeholder="Min length(3)" required>

Now, whenever the form control is touched or its value changes and validation fails, a validation tooltip should pop up to notify you.

How to customize the error messages

By default, this package only provides a simple english message, but you can hook your own message creation logic.

Create a new service that implements the NbErrorNormalizerInterface. In the normalize method you can hook whatever logic you need (translations, etc...) to show your error message. If you want to show the default value, just return null.

import {Injectable} from '@angular/core';
import {NbErrorNormalizerInterface, NbErrorNormalizerResult} from '@sungazer/nebular-validation-errors';

@Injectable({
  providedIn: 'root'
})
export class ErrorNormalizerService implements NbErrorNormalizerInterface {

  constructor() {
  }

  normalize(errors: any): NbErrorNormalizerResult {
    if (errors.required) {
      return {message: 'This field is required'};
    }
    return null;
  }
}

After creating the service, register it as a provider in the AppModule.

import {NB_ERROR_NORMALIZER} from '@sungazer/nebular-validation-errors';

@NgModule({
  declarations: [
    //...
  ],
  imports: [
    //...
  ],
  providers: [
    {provide: NB_ERROR_NORMALIZER, useClass: ErrorNormalizerService},
  ],
  //...
})
export class AppModule {
}

How to customize the tooltip placement

Tooltip placement and adjustment (see Nebular docs for details) can be customized in 2 places:

  • At the module level (import the module using the withConfig helper, i.e. NbErrorTooltipModule.withConfig({...}))
  • At the single directive level (use nbErrorTooltipPosition and nbErrorTooltipAdjustent attributes)