Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Integrate
dylint
lints to build #1412Integrate
dylint
lints to build #1412Changes from all commits
b1a4d65
f736546
ddabef6
7946de2
f2cb3de
8f392c4
d74f7ca
1d15601
83df3fb
d197c76
8950df2
577fa72
b3cbec9
f21e2b8
8b7c7f3
c7a0626
af380eb
6c4be8d
9fb5222
4a22459
a97de2f
557a696
45c531f
823dac9
3d4af86
84780ba
01dd588
44cf7b1
38c8bcd
f3212f3
284f0ff
df89a75
789087c
169da84
a86c38b
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't like that all the lints will be executed on each build, because it slows down the build process and may bother the user with extra noise generated by lints. Ideally, we should execute only mandatory lints needed to check compilation errors (like
no_main
) and skip the rest.I think the most simple way to do this is to split our
ink_linting
in twodylint
libraries, likeink_linting
andink_linting_extra
. The first one will contain only the mandatory lints, and the second one will run the optional analyses when user requesting it.There are other ways to suppress lints (like hacking
Cargo.toml
in contract projects or compilation flags forrustc
), but AFAIK these will execute lints anyway, suppressing their output.WDYT @ascjones?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes we only want the mandatory lints to execute every time, extra lints must still be opt-in.
Sounds good to me 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Merged use-ink/ink#2032 now