feat: add support for configuration error severities in analysis_options.yaml

[Artur-Wisniewski]

Closes issue: ISSUE-323

Now it is possible to override error severities from analysis_options.yaml using the errors parameter inside custom_lint

You should be able to do this:

custom_lint:
  errors:
    some_lint_with_info_severity: error

All of the some_lint_with_info_severity lint's error messages will be shown as errors by the analyzer

[vercel]

@Artur-Wisniewski is attempting to deploy a commit to the Invertase Team on Vercel.

A member of the Team first needs to authorize it.

[docs-page]

To view this pull requests documentation preview, visit the following URL:

docs.page/invertase/dart_custom_lint~326

Documentation is deployed and generated using docs.page.

[rrousselGit]

Thanks for this!

Those tests are a bit too tied to the implementation details for my liking. Could you write e2e tests instead?

Like running dart run custom_lint and verify that the console flags a diagnostic as WARNING instead of INFO.

[Artur-Wisniewski]

Thanks for this!

Those tests are a bit too tied to the implementation details for my liking. Could you write e2e tests instead?

Like running dart run custom_lint and verify that the console flags a diagnostic as WARNING instead of INFO.

Hello @rrousselGit 👋🏻
I've managed to add some additional tests for this task. (packages/custom_lint/test/analysis_options_test.dart)
If I understand correctly, these should be counted as e2e tests.

Please don't hesitate to let me know if there is anything else you need here.

[rrousselGit]

Isn't this covered by the previous tests? I'd rather not have tests that are so tied to the implementation details.

[Artur-Wisniewski]

You're right. I will remove this test because it isn't needed here, and as you said, it is too much tied to the implementation details (now I see it).