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

@turbo-red/strapi-plugin-lookup-enum

v1.0.1

Published

Like enum field, but options are extracted from a field provided by a single-type content.

Downloads

132

Readme

Strapi plugin lookup-enum

A strapi plugin that adds custom fields similar to the enum field, but values are extracted from a field provided by a single-type content, so options are dynamic.

These two component have been created to satisfy all those cases where you need to set one value string or a group of them from a dynamic set.

Without these two component you would generally need a collection type for every field and link with a relation, definitely not very efficient when you have to deal with simple cases.

These two field types simplifies this design parsing text from fields in a selected single-type entity.

For lookup-enum field the value will be a string, while for multi-lookup-enum the value will be an array of stings.

CHANGELOG

1.0.0

  • First release

Installation

To install this plugin, you need to add an NPM dependency to your Strapi application:

# Using Yarn
yarn add @turbo-red/strapi-plugin-lookup-enum

# Or using NPM
npm install @turbo-red/strapi-plugin-lookup-enum

Then, you'll need to build your admin panel:

# Using Yarn
yarn build

# Or using NPM
npm run build

Usage

After installation you will find the lookup-enum and multi-lookup-enum in the custom fields section of the content-type builder.

Content-Type builder

Suppose you have to create a collection-type to store data for html pages and you want to be able to define a custom template and a set of css classes for each item.

First create a single-type entity with two text fields that you can fill like in the example below:

css classes

Then define a Page collection-type in the content-type builder:

Add a lookup-enum custom field and name it template.
Select api::css-classes.css-classesfrom the Single-Type field in the Options Source, then write template as the name of the field you want to become the lookup source field.

Add a multi-lookup-enum too, this time write pageCssClass as lookup source field.

Finally add a content and all the fields you need for your Page collection-type.

template lookup-enum definition

When you edit page entries in Content Manager you will find a form similar to the following:

page entry example

As you can see entries are selected from the css-classes parsed fields.

And that's all, happy coding!