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

@one-profile/core

v0.8.4

Published

Core package for one profile application

Downloads

388

Readme

one-profile-core

Core package for one profile application

Installation

yarn

yarn add @one-profile/core

npm

npm install @one-profile/core

APIs

oneProfileSetup

oneProfileSetup is the bootstrap API that will help you to expose your application/parcel to OneProfile ecosystem

import React from "react";
import Root from "./root.component";
import { oneProfileSetup } from "@one-profile/core";

const profileSetup = oneProfileSetup(Root);
export const { bootstrap, mount, unmount, config } = profileSetup;

arguments

rootComponent: React.FunctionComponent<any>

React root functional component that is mounted into OneProfile

config: OneProfileSetupConfig (optional)

  • activationFn: Promise<boolean> A function that decides whether to activate the current application. Expected to return a promise of boolean to be used in one profile initialisation. Function accepts accessToken and current user's oauth claim details
import {UserClaims} from "@okta/okta-auth-js";
import {User} from "@one-profile/core";

function activateProfile(accessToken, currentUser: User & UserClaims) {
  return new Promise<boolean>((resolve) =>
    makeSomeExternalCall(accessToken, currentUser).then((result) => {
      if (result == "success" && currentUser.homeOffice.countryIsoCode == "IND") {
        resolve(true);
      } else {
        resolve(false);
      }
    })
  );
}

//...
//...
//some business logic in between
//...
//...
const profileSetup = oneProfileSetup(Root, {
  activationFn: activateProfile,
});

External APIs

users.getMe

users.getMe is the users API that will expose current logged-in user

import React from "react";
import { oneProfileSetup, users } from "@one-profile/core";

function someFunctionRequireCurrentUser(){
  // get access token either using context or props from root component
  users.getMe(accessToken).then((user:User) => { 
    // user data
  });
}

arguments

accessToken (required)

accessToken used to authorise the getUser API request

response

User

{
  name: string;
  email: string;
  grade: {
    name: string;
  }
  role: {
    name: string;
  }
  department: {
    id: string;
    name: string;
  }
  homeOffice: {
    name: string;
    countryIsoCode: string;
    country: string;
    locationCode: string;
  }
  workingOffice: {
    name: string;
    countryIsoCode: string;
    country: string;
    locationCode: string;
  };
}

error data (refer ResponseError)

{
  message: string;
}

Error Handling

responseError

Response Error is thrown which can be caught in the API's promise catch mechanism

Usage:

import { ResponseError } from "@one-profile/core";

api.then(console.log).catch((error: ResponseError) => {
  if (error.status == 404) {
    //404 or 500
    console.log(error.data);
  }
});

Jest Setup

Make sure you include the following line in jest setup. Make sure you install regenerator-runtime package

import 'regenerator-runtime/runtime';