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

guarded-components

v0.0.18

Published

A jsx tag for hiding or providing action on components

Downloads

11

Readme

guarded-components

This is used to protect pages or components such as buttons based on the user's state. It seems that this is a common problem in industry and there are no packages that I am aware of which work for most jsx compatible frameworks with any authorization strategies. This package allows the user to take control of this problem by simply defining strategies based on contracts which they determine.

details

| Importables | about | | ----------- | ----------- | | Guard | this is the jsx component which will be wrapped around a child component or a page. It takes either a single strategy or an array of strategies under the strategy prop. Additionally there is the hide prop which if included will cause the children to be hidden on failure to support the contract | | createStrategy | this is a function which is used to make a strategy. It takes a contract. A contract is an object which has three fields. Shall, get, and breach. Shall is an identification which must be matched. This could be any type of value but I recommend string or number. get is a function which takes no input but returns the current state of the user. Breach is the action which shall be taken if the contract is broken. Breach however will not be enacted if hide is attached to the guard as hide is the action which is taken |

example

This is a basic example showing the different types of guards that you could have. Note the differences in the contracts and the combination of strategies.

import {Guard, createStrategy} from "guarded-components";
 
const loggedin = createStrategy(
  {
    shall: true,
    get: ()=>user.isLoggedin(),
    breach: ()=>{window.href.location = "www.website.com/login"}
  },
);
 
const admin = createStrategy(
  {
    shall: "admin",
    get: ()=>user.getRoles().admin,
    breach: ()=>{window.href.location = "www.website.com"}
  },
);
 
<Guard
    strategy={loggedin}
>
    Make sure you are loggedin otherwise you are getting redirected!
</Guard>
<br></br>
<Guard
    strategy={admin}
    hide
>
    If you aren't an admin you can't see me.
</Guard>
<br></br>
<Guard
    strategy={[admin, loggedin]}
>
    You have to be an admin AND loggedin :/
</Guard>
<br></br>
<Guard
    strategy={[admin, loggedin]}
>
    You have to be an admin AND loggedin :/
</Guard>

This should theoretically support things such as react-redux. However I have not tested it. It would probably look something like this. You might need to use a useRef for the selector

//This is an example contract if you were using something like react-redux
const state = useSelector((store)=>store.admin.state);
 
{
    shall: "admin"
    get: ()=>{state},
    breach: ()=>{alert("NO YOU CANT DO THAT!")}
}