Skip to content

Mixin lint #2485

Answered by carolynvs
tamirkamara asked this question in Q&A
Discussion options

You must be logged in to vote

Oops, that message should only be displayed as a debug message, but it's being printed at info level as well. I must have caused that regression when fixing the ordering of calling mixins during build.

Mixins are not required to implement a lint command. If a mixin does implement it, then porter will parse the results and if any of the results are errors (mixins can also report warnings), then lint fails. Since lint is called automatically before build, this can fail builds as well. You can bypass linting during build with the --no-lint flag.

This isn't documented well, but I'd welcome contributions to the docs! We have #2486 which tracks documenting the lint codes returned. Right now the…

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by tamirkamara
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants