Use explicit constructor for QSslCertificate with value initialized argument

Previously the BluetoothDeviceLink::certificate() method was returning a
value initialized object which I believe default initializes the object.
However, Clang throws a build error at this because QSslCertificate has
explicit constructors. This change uses one of those constructors and
uses value intialization to default construct/initialize the argument
for it. It fixes the build and hopefully doesn't break anything since
this is a TODO anyways!

BUG: 469428

Signed-off-by: Ali Abdel-Qader <abdelqaderali@protonmail.com>
(cherry picked from commit bbac0aa085)
This commit is contained in:
Ali Abdel-Qader 2023-05-06 15:51:53 -04:00 committed by Andreas Sturmlechner
parent 0b475472f2
commit 8687f8cfda
No known key found for this signature in database
GPG key ID: C5D682DFAEFD8888

View file

@ -99,5 +99,5 @@ void BluetoothDeviceLink::dataReceived()
QSslCertificate BluetoothDeviceLink::certificate() const
{
return {}; // TODO Not sure what to do here. For LanDeviceLink we use the SSL connection's certificate, but we don't have that here
return QSslCertificate({}); // TODO Not sure what to do here. For LanDeviceLink we use the SSL connection's certificate, but we don't have that here
}