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

solhint-plugin-modifiers

v0.0.3

Published

solhint plugin for linting function modifiers. Ensure modifiers are present in certain files, contracts, and methods with flexible matching.

Downloads

157

Readme

solhint-plugin-modifiers

npm version

solhint plugin for linting function modifiers. Ensure modifiers are present in certain files, contracts, and methods with flexible matching.

Installation

Available on npm:

npm install solhint-plugin-modifiers --save-dev

Usage

Enable the plugin in your project's .solhint.json:

{
  "extends": "solhint:recommended",
  "plugins": ["modifiers"],
  "rules": {
    "modifiers/ensure-modifiers": ["error", {
      "required": {
        "*": ["onlyAdmin"]
      }
    }]
  },
}

The above configuration will require the onlyAdmin modifier on all methods for all contracts in all linted files.

You can use globbing to limit the required modifiers:

{
  "required": {
    "contracts/core/*.sol": {
      "Contract.method": ["onlyAdmin"],
      "Contract": {
        "method": ["onlyAdmin"]
      },
    },
    "contracts/core/*.sol:Contract.method": ["onlyAdmin"],
    "contracts/core/*.sol:Contract": {
      "method": ["onlyAdmin"],
    },
  }
}

All of the rules in the previous example are equivalent. That is, they require the onlyAdmin modifier for Contract.method defined inside some solidity file in contracts/core/.

The file path, contract name, and method may all be globbed e.g.

{
  "required": {
    "contracts/core/*.sol": {
      "*.transfer": ["onlyAdmin"],
      "Token.*": {
        "transfer": ["onlyMinter"]
      },
    },
  }
}

If Token.transfer is defined in contracts/core/Token.sol, then it will be matched by both rules. Note that matching modifiers are unioned, so Token.transfer would require both onlyAdmin and onlyMinter modifiers.

Overrides

You might want to require a modifier everywhere by default but explicitly override the requirement for some methods. You can use the override key to achieve this:

{
  "required": {
    "*": ["onlyAdmin"]
  },
  "override": {
    "*.sol:Contract.method": []
  }
}

With this configuration, Contract.method is overridden to require no modifiers, but all other methods require the onlyAdmin modifier.

Other configuration options

Default configuration is:

{
      "ignoreVisibility": ["internal"],
      "ignoreStateMutability": ["view", "pure"],
      "ignoreContractKind": ["abstract", "interface"],
      "verbose": false,
      "required": {},
      "override": {}
}

In other words, internal, view, and pure methods are ignored by default, as are methods in abstract or interface contracts.