Using dynamic error codes?

[dickermoshe]

The docs for LintRule state that [LintRule]s should avoid emitting lints that use a code different that [code].

dart_custom_lint/packages/custom_lint_core/lib/src/lint_rule.dart

Lines 64 to 67 in 90365e2

	/// The [LintCode] that this [LintRule] may emit.
	///
	/// [LintRule]s should avoid emitting lints that use a code different that [code].
	final LintCode code;

Q1: Why?
Q2: What about if the code name stays the same but the problemMessage changes

Use Case: We would like to use our code generator (drift_dev) with the custom_lint to find errors. The errors emitted can be of many types.

[rrousselGit]

Q1: Why?

To disable lints in analysis_options.yaml and when writing // ignore_for_file: code.

Q2: What about if the code name stays the same but the problemMessage changes

That's fine. But LintCode already supports dynamic messages.

You can do problemMessage: 'Hello {0}'

then used as errorReporter.atNode(node, arguments: ['msg']) // The message will be Hello msg

[dickermoshe]

@rrousselGit Have you given any thought about using custom_lint on the to build the code live instead of using build_runner?

Would Seem like macros!

[rrousselGit]

I have no clue what you're referring to. Custom_lint doesn't even use build_runner :)

[dickermoshe]

Background

The code generator for drift is pretty flexible.
Our main implementation of the code generator works with build_runner, which uses all the great tools build_runner has to offer for parsing and navigating dart code.

However we built a second code generator which works with just a simple AnalysisSession.

But why?

Well, when we started writing a custom_lint plugin, we realized, "Hey, our code generator already parses the source code and spits out errors, why are we doing writing this twice?!

So we built a version of our code generator which can work with what custom_lint gives us.

Now we can extract all of these errors and put them we they need to be

Results

Now errors which would normally only be emitted when running dart run build_runner build, are show in the editor!

Idea

Instead of just running the code generator under the hood to find errors, why not actually write the code too!