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

Add Linter to Stage Command #1454

Closed
jribbink opened this issue Mar 14, 2024 · 1 comment
Closed

Add Linter to Stage Command #1454

jribbink opened this issue Mar 14, 2024 · 1 comment
Assignees
Labels
Feature A new user feature or a new package API Feedback

Comments

@jribbink
Copy link
Contributor

Instructions

Issue To Be Solved

We should add the Cadence potentially as a preflight check that contracts going to be updated to C1.0 are valid/provide feedback if not. This is a sanity check as well as a useful feedback touchpoint for developers.

@jribbink jribbink added Feature A new user feature or a new package API Feedback labels Mar 14, 2024
@jribbink jribbink self-assigned this Mar 14, 2024
@jribbink jribbink moved this to Cadence 1.0 Triage in 🌊 Flow 4D Mar 14, 2024
@gregsantos gregsantos moved this from Cadence 1.0 Triage to 🔖 Ready for Pickup in 🌊 Flow 4D Mar 14, 2024
@jribbink
Copy link
Contributor Author

Closing this because it's probbly not necessary. The update validator & Cadence checker do a pretty good job already and I think naturally users will try to solve these in VSCode, etc. and get linting info there. So it's probably unnecessary to bloat this commnd further/incur the technical burden.

@github-project-automation github-project-automation bot moved this from 🔖 Ready for Pickup to ✅ Done in 🌊 Flow 4D Apr 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature A new user feature or a new package API Feedback
Projects
Archived in project
Development

No branches or pull requests

1 participant