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

@btapai/ng-authorisation

v0.0.1

Published

An authorisation handler library for angular applications

Downloads

4

Readme

Authorisation

How to install

Install the package with the following script:

npm install @btapai/ng-authorisation

or

yarn add @btapai/ng-authorisation

How to use

Import the module into your main ngModule and in lazy-loaded modules where you would like to use the directive. Inside your main ngModule, provide the AUTHORISATION_HANDLER injection token and use your service, which implements the AuthorisationInterface interface. If you'd like to use the extra styling functionality, you can provide the AUTHORISATION_CLASS injection token and use your own "unauthorised" css class name.

import { BrowserModule } from '@angular/platform-browser';
import { NgModule } from '@angular/core';
import { AppComponent } from './app.component';
import { AuthorisationModule, AUTHORISATION_HANDLER, AUTHORISATION_CLASS } from '@btapai/ng-authorisation';

@NgModule({
  declarations: [AppComponent],
  imports: [BrowserModule, AuthorisationModule],
  providers: [
    { provide: AUTHORISATION_HANDLER, useClass: YourAuthorisationService },
    { provide: AUTHORISATION_CLASS, useValue: 'your-specific-class' },
  ],
  bootstrap: [AppComponent],
})
export class AppModule {}

Add the authorisation structural directive to your template using the asterisk (*) syntax, to prevent displaying components if the user does not have READ access.

<div *authorisation="'BIG_RED_BUTTON'">
  The div won't be part of the DOM if the user does not have READ access.
</div>

If you would like to disable a button, or a template-driven form input, you can use the directive's WRITE access checker method.

<div *authorisation="'BIG_RED_BUTTON'; let hasOnlyReadAccess">
  The "hasOnlyReadAccess" method will return the provided boolean if the user has write access,
  otherwise, the button is disabled.
  <button [disabled]="hasOnlyReadAccess(isDisabled)">BIG RED BUTTON</button>
</div>

You can also disable reactive form controls, groups and arrays as well, passing the formControl as the control parameter

<div *authorisation="'BIG_RED_BUTTON'; control: formControl">
  <div>
    <label for="simpleControl">Simple FormControl bound using [formControl]</label>
    <input id="simpleControl" [formControl]="formControl" />
  </div>
</div>
<form *authorisation="'LAUNCH_CODE_INPUTS'; control: launchCodesForm" [formGroup]="launchCodesForm">
  <label for="primary-high-ranking-officer">First officer access code:</label>
  <input id="primary-high-ranking-officer" formControlName="firstOfficerAccessCode" />

  <label for="secondary-high-ranking-officer">Second officer access code:</label>
  <input id="secondary-high-ranking-officer" formControlName="secondOfficerAccessCode" />
</form>

This authorisation directive might not be sufficient to your authorisation handling needs, but feel free to copy the code and make the necessary changes for yourself. Please, if you do so, throw me a tweet @TapaiBalazs