mirror of
https://github.com/valitydev/openapi-generator.git
synced 2024-11-07 10:58:55 +00:00
24c55d1f0e
* Changing QBuffer to use a QByteArray solves the issue for me since there is no real use-case for using a QBuffer. Documentation of QT5 states: QBuffer::QBuffer(QByteArray *byteArray, QObject *parent = Q_NULLPTR) Constructs a QBuffer that uses the QByteArray pointed to by byteArray as its internal buffer, and with the given parent. The caller is responsible for ensuring that byteArray remains valid until the QBuffer is destroyed, or until setBuffer() is called to change the buffer. QBuffer doesn't take ownership of the QByteArray. Since the variable “request_content” is allocated on the stack, this is clearly wrong and a bug. The construction of QBuffer is designed this way so that whenever you write to the buffer, it is also written to the byte array that it is pointing to * Add a retro-compatible solution based on QNetworkAccessManager SourceCode * update samples |
||
---|---|---|
.. | ||
swagger-codegen | ||
swagger-codegen-cli | ||
swagger-codegen-maven-plugin | ||
swagger-generator |