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

@scriptrunnerhq/vendors-api

v1.0.6

Published

This library will allow you to integrate your custom field with Behaviours for ScriptRunner for Jira Data Center.

Downloads

7,410

Readme

ScriptRunner Vendors API

This library will allow you to integrate your custom field with Behaviours for ScriptRunner for Jira Data Center.

This API will be supported in ScriptRunner for Jira in an upcoming version yet to be determined.

Installation

  1. Add @scriptrunnerhq/vendors-api to your package.json.
  2. Run npm install or yarn install.
  3. In the server-side template file add two data properties to the root node:
    • data-scriptrunner-vendors-api-cfid - with the value of custom field ID.
    • data-scriptrunner-vendors-api-stored-value - with the value stored in the database.
  4. In your custom field code, ensure that VendorsApi.init() is called immediately when your field is initialized.

VendorsApi.init()

VendorsApi.init() is how you connect your custom field with ScriptRunner Behaviours. It takes two arguments:

  1. customFieldId - the unique ID assigned by Jira for the field.
  2. apiSpec - an object with API functions:
    • getValue() - return the current value of custom field.
    • setValue(value) - set value of the custom field.
    • setReadOnly(readOnly) - enables or disables the custom field based on readOnly boolean argument.
    • bindOnChange(callback) - a callback to inform ScriptRunner Behaviours that the value of the custom field has changed.
    • setOptions(options) - (optional) for fields like select provides a list of available options in the form of {key: string, value: string}[].
    • isPopulated() - (optional) determines if the field is populated with data, to inform ScriptRunner of mandatory fields not filled in.

Note: The getValue() and setValue() should be symmetric, meaning both should return/accept values in the same format. These values should match the data format stored in the database.

It is important to call VendorApi.init() as early as possible, as any of the above functions may be called early from ScriptRunner Behaviours. This means that all of the above can be called before the custom field is fully initialized. For this reason all of the above can return Promise and internally wait for custom field initialization to finish before applying a Behaviour.

More information and an example plugin can be found in our Documentation.

We also provide an example plugin demonstrating how this API can be used.