MarkdownBear is not very helpful

[underyx]

https://gitlab.com/underyx/dotfiles/builds/1640916

I got an error message that

The text does not comply to the set style.

and I have no idea what to do with this, especially since coala is providing the settings and I don't even see them :(

[gitmate-bot]

Thanks for reporting this issue!

Your aid is required, fellow coalaian. Help us triage and solving this issue!

CC @sils1297, @AbdealiJK

[AbdealiLoKo]

I think you can check the default settings with coala -B -I -b MarkdownBear
And also, if you set the default action to be "ShowPatchAction" you can see the suggested changes which helps to understand why coala gave that Result :)

Although, I agree that the error message is bad and these are just workarounds for you right now.

[underyx]

@AbdealiJK thanks for the tips! Sadly, after this change to the .coafile the output still doesn't help: https://gitlab.com/underyx/dotfiles/builds/1641088

[AbdealiLoKo]

Oops, sorry.

The reason it does not work is because coala-ci is "Non Interactive" and so actions cannot be applied (they're skipped).
The discussion about this was at coala/coala#1526 which led to coala/coala#1546 and both never got solved ...

[Makman2]

It's a general problem to combine patches and help text from linters as they don't provide both.

It's possible to run the linter twice (very bad for performance), and relating issue text to the patches. But this won't work always dependent on the complexity of an issue.

Optimally linters need to support a new output format, that shows messages and patches combined. Then we can achieve perfect results.

[bkhanale]

This issue is reserved under the GSoC project Improve Generic Bear Quality.

[bkhanale]

Couldn't find a stable solution for this issue. The 'warnings' emitted by the remark-lint are inadequate also they are not in sync with the patches being offered by the tool. If something changes, we might still be able to fix this. But, I think we should get more bears for markdown.

[eli-halych]

I experienced a similar problem, probably the same one.

For me it said

The text does not comply to the set style.
[INFO][15:51:17] Applied 'ShowPatchAction' on '/mypath/README.md' from 'MarkdownBear'.

I noticed that every linter wants a new line at the end of every file. So my README.md didn't have this new line. Once I added it, the problem disappeared.