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

angular-aems

v0.0.5

Published

API Entity Management Service for Angular

Downloads

2

Readme

AngularAems

This is an experimental implementation of an API Entity Management Service for Angular.

Install

Run yarn add angular-aems in your project root.

Usage

Step 1

Import AngularAemsModule in your app.

import { AngularAemsModule } from 'angular-aems';

@NgModule({
  imports: [
    AngularAemsModule
  ]
})
export class AppModule {
}

Step 2

Inject EntityService into your component and set the apiBaseUrl.

import { Component, OnInit } from '@angular/core';

import { EntityService } from 'angular-aems';

import { Event } from './_interfaces/event.interface';

@Component({
  selector: 'app-root',
  template: `<h2>Events</h2>
  <ul>
    <li *ngFor="let event of events">{{ event.title }}</li>
  </ul>`
})
export class AppComponent implements OnInit {
  events: Event[];

  constructor(
    private eventService: EntityService<Event>
  ) {
    eventService.config = {
      apiBaseUrl: 'events'
    };
  }

  ngOnInit() {
    this.eventService.getAll().subscribe(events => this.events = events);
  }
}

API

Service types

There are three kinds of services to help getting the job done.

  • Service
  • Transformer
  • Resource

Service

The Service is the only "public" service you want to use directly in your code. Methods exists for read, write, update and delete one or more items.

If you extend the EntityService, the following methods are available:

  /**
   * Set configuration for this instance
   * @param config Object of type EntityConfig.
   */
  setConfig(config: EntityConfig): void {
    this.config = config;
  }

  /**
   * Get one item.
   * @param id Id of the item you want to get.
   */
  getOne(id: number): Observable<T> {
    return this.resource.getOne(id, this.config.apiBaseUrl).pipe(
      map((entity: T) => this.transformer.backendToFrontend(entity))
    );
  }

  /**
   * Get all items
   */
  getAll(): Observable<T[]> {
    return this.resource.getAll(this.config.apiBaseUrl).pipe(
      map((entities: T[]) => entities.map(x => this.transformer.backendToFrontend(x)))
    );
  }

Transformer

The Transformer is the service, which is internally used to transform the data from the frontend interface (used in our application) with the backend interface (provided by the rest endpoint).

Resource

The Resource is the part of the concept, which talks to the backend.