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

@smartbit4all/document-explorer

v4.0.6

Published

1. Create a project-specific subclass from the `DocuStoreExplorerPageApi` interface and its implementation.

Downloads

401

Readme

SmartDocuStoreExplorer

How to setup

  1. Create a project-specific subclass from the DocuStoreExplorerPageApi interface and its implementation.
public interface YourDocuExplorerPageApi extends DocuStoreExplorerPageApi {}

public class YourDocuExplorerPageApiImpl extends DocuStoreExplorerPageApiImpl
    implements YourDocuExplorerPageApi{}
  1. Create a project-specific subclass from the DocuStoreFolderPageApi interface and its implementation.
public interface YourDocuFolderPageApi extends DocuStoreFolderPageApi {}

public class YourDocuFolderPageApiImpl extends DocuStoreFolderPageApiImpl
    implements YourDocuFolderPageApi {
  1. Create project-specific view names that you provide in the @ViewApi annotations.
@ViewApi(value = YourViewNames.YOUR_DOCU_EXPLORER,
    parent = YourViewNames.SOME_PARENT)
public interface MebitDocuExplorerPageApi extends DocuStoreExplorerPageApi {}

@ViewApi(value = YourViewNames.YOUR_DOCU_FOLDER,
    parent = YourViewNames.YOUR_DOCU_EXPLORER)
public interface YourDocuFolderPageApi extends DocuStoreFolderPageApi {}
  1. In your project's UI configuration, use the @Bean annotation to define your derived interfaces and implementations.
  @Bean
  public DocuStoreFolderPageApi folderPageApi() {
    return new YourDocuFolderPageApiImpl();
  }

  @Override
  @Bean
  public DocuStoreExplorerPageApi docuStoreExplorerPageApi() {
    return new YourDocuExplorerPageApiImpl();
  }
  1. Install the @smartbit4all/document-explorer npm package into your Angular project. @smartbit4all/document-explorer
  2. In the Pages.ts file, specify the names of the new pages.
export enum Pages {
    ...
    YOUR_DOCU_EXPLORER = 'YourDocuExplorer',
    YOUR_DOCU_FOLDER = 'YourDocuFolder',
}
  1. In the viewHandlers.ts file, assign the URLs corresponding to the view names.
export const viewContextHandlers: SmartViewHandlerModel[] = [
    ...
    {
    name: Pages.YOUR_DOCU_EXPLORER,
    route: 'your/route/for the component',
  },
  {
    name: Pages.YOUR_DOCU_FOLDER,
    route: 'your/route/for the component',
  },
  1. Configure the Angular routing according to your needs.

  2. In the app.module.ts provide the DocuStoreExplorer viewname and the project AuthenticationService like this:

providers: [
    ...
    {
      provide: 'AuthenticationService',
      useClass: AuthenticationService,
    },
    {
      provide: 'pageName',
      useValue: Pages.SUBSTANCE_DOCU_EXPLORER,
    },
  ],