Skip to content

Ensure all linter messages are originated from a LinterMessage - #2651

Open
soapy1 wants to merge 2 commits into
conda-forge:mainfrom
soapy1:ensure-all-lints-have-LinterMessage
Open

Ensure all linter messages are originated from a LinterMessage#2651
soapy1 wants to merge 2 commits into
conda-forge:mainfrom
soapy1:ensure-all-lints-have-LinterMessage

Conversation

@soapy1

@soapy1 soapy1 commented Aug 11, 2026

Copy link
Copy Markdown

The goal of this pr is to ensure that all linter lints and hints have a LinterMessage that they originate from. This will ensure being able to output structured data for all lints/hints. All added LinterMessages are existing messages.

  • Introduces new LinterMessage:
    • UnsupportedSchemaVersion - was previously a string appended to the list of lints
    • InvalidLicenseFamily - was previously wrapping a conda-build error as a string and adding it to the list of lints
    • TypeMustBeADictionary - was previously a string error message
    • TypeMustBeAListOrDictionary - was previously a string error message

split out from #2646

Checklist

  • Added a news entry with any new deprecations added to the Deprecated section.
  • [ ] Regenerated schema JSON if schema altered (python -m conda_smithy.schema)
  • Regenerated linter documentation if any rules were added, removed or modified (python -m conda_smithy.linter.messages)

"""

kind = "lint"
identifier = "R0-008"

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

This can also apply to v1 recipes. Though, in practice (currently) this lint will only ever be added to a v0 recipe.

@soapy1
soapy1 marked this pull request as ready for review August 11, 2026 16:05
@soapy1
soapy1 requested a review from a team as a code owner August 11, 2026 16:05
@soapy1
soapy1 force-pushed the ensure-all-lints-have-LinterMessage branch from 174dbbd to 3d4defc Compare August 11, 2026 16:05
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.

1 participant