c3f6c3dd82
The Modrinth changelog is fairly straight-forward, as it's given to us directly with the API call we already did. Flame, on the other hand, requires us to do another call to get the changelog, so it can introduce quite a heavy performance impact. This way, we make it optional to get such changelog. Signed-off-by: flow <flowlnlnln@gmail.com>
23 lines
692 B
C++
23 lines
692 B
C++
//
|
|
// Created by timoreo on 16/01/2022.
|
|
//
|
|
|
|
#pragma once
|
|
|
|
#include "modplatform/ModIndex.h"
|
|
|
|
#include "BaseInstance.h"
|
|
#include <QNetworkAccessManager>
|
|
|
|
namespace FlameMod {
|
|
|
|
void loadIndexedPack(ModPlatform::IndexedPack& m, QJsonObject& obj);
|
|
void loadExtraPackData(ModPlatform::IndexedPack& m, QJsonObject& obj);
|
|
void loadIndexedPackVersions(ModPlatform::IndexedPack& pack,
|
|
QJsonArray& arr,
|
|
const shared_qobject_ptr<QNetworkAccessManager>& network,
|
|
BaseInstance* inst);
|
|
auto loadIndexedPackVersion(QJsonObject& obj, bool load_changelog = false) -> ModPlatform::IndexedVersion;
|
|
|
|
} // namespace FlameMod
|