[Development] qmllint's MaxWarnings and how to detect commits introducing new qmllint warnings
Albert Astals Cid
aacid at kde.org
Tue Aug 11 00:37:38 CEST 2026
El diumenge, 9 d’agost del 2026, a les 22:33:27 (Hora d’estiu d’Europa
central), Sérgio Martins via Development va escriure:
> On 2026-08-04 15:14, Sami Shalayel via Development wrote:
> > Hi everyone,
> >
> >
> > TL;DR: How do you detect commits that introduce new qmllint warnings
> > in your projects, and do you need a mechanism for that in qmllint?
> >
> > (...)
>
> Hi,
>
> I use MaxWarnings=0 and insert suppressions like "// qmllint disable
> <category>" if needed.
Same. Usually with a .qmllint.ini per folder, in the hierarchy so I can be
more strict in some folders and less in others.
Cheers,
Albert
>
> If it's an old project with thousands of warnings, then instead, I edit
> .qmllint.ini and set all categories to "info" and only bump
> them to "warning" once they're clean.
>
>
> Regards,
More information about the Development
mailing list