[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: Banning QNetworkAccessManager
From:       Albert Astals Cid <aacid () kde ! org>
Date:       2020-02-20 22:40:43
Message-ID: 9653151.nUPlyArG6x () xps
[Download RAW message or body]

El dijous, 20 de febrer de 2020, a les 14:29:47 CET, Allen Winter va escriure:
> On Wednesday, February 19, 2020 6:09:02 PM EST Albert Astals Cid wrote:
> > El dimecres, 19 de febrer de 2020, a les 9:28:22 CET, Volker Krause va escriure:
> > > Additionally, improved documentation, a possible KNAM and/or driving the QNAM 
> > > changes upstream can still be done alongside this obviously.
> > 
> > Also for Qt5 which will probably never be changed a clazy warning and making it \
> > easy to run clazy on gitlab CI would be great. 
> 
> Krazy has a checker for QNetworkAccessManager use in Qt4 code.
> I could add a checker for Qt5 code if someone tells me what to look for
> (not that many people look at krazy reports. couldn't hurt. might help.

There's other ways to do it, but i guess we could start with something that checks \
for this?

https://community.kde.org/Policies/API_to_Avoid#QNetworkAccessManager

Cheers,
  Albert


[prev in list] [next in list] [prev in thread] [next in thread]