Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ci: use lintspec instead of natspec-smells #98

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

0xteddybear
Copy link
Contributor

This is part of the soft-deprecation of natspec-smells started in defi-wonderland/natspec-smells#67

@@ -17,7 +17,7 @@
"deploy:sepolia": "bash -c 'source .env && forge script Deploy --rpc-url $SEPOLIA_RPC --account $SEPOLIA_DEPLOYER_NAME --broadcast --verify --chain sepolia -vvvvv'",
"lint:check": "yarn lint:sol && forge fmt --check",
"lint:fix": "sort-package-json && forge fmt && yarn lint:sol --fix",
"lint:natspec": "npx @defi-wonderland/natspec-smells --config natspec-smells.config.js",
"lint:natspec": "lintspec src -f variable",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

how come you are using lintspec here without adding it to the package.json? I believe the dependency is missing, I don't recommend expecting people to instal it globally

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lintspec is not distributed via npm. CI installs it via a specific action for cargo packages, and I modified the README to instruct users to install it globally via cargo. I think this is acceptable given it's what we already do for bulloak. Other alternatives are:

  • push to get lintspec released on npm (should be possible to distribute a binary I think)
  • migrate the entire boilerplate to use nix instead of npm?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants