refactor: make mod metadata presence (or lack of) easier to find out

This commit is contained in:
flow
2022-04-20 18:45:39 -03:00
committed by flow
parent a99858c64d
commit 96e36f0604
6 changed files with 49 additions and 13 deletions

View File

@ -41,7 +41,6 @@ public:
auto dateTimeChanged() const -> QDateTime { return m_changedDateTime; }
auto internal_id() const -> QString { return m_internal_id; }
auto type() const -> ModType { return m_type; }
auto fromMetadata() const -> bool { return m_from_metadata; }
auto enabled() const -> bool { return m_enabled; }
auto valid() const -> bool { return m_type != MOD_UNKNOWN; }
@ -52,10 +51,14 @@ public:
auto homeurl() const -> QString;
auto description() const -> QString;
auto authors() const -> QStringList;
auto status() const -> ModStatus;
auto metadata() const -> const std::shared_ptr<Metadata::ModStruct> { return details().metadata; };
auto metadata() -> std::shared_ptr<Metadata::ModStruct> { return m_localDetails->metadata; };
void setStatus(ModStatus status);
void setMetadata(Metadata::ModStruct* metadata);
auto enable(bool value) -> bool;
// delete all the files of this mod
@ -82,7 +85,6 @@ protected:
/* Name as reported via the file name */
QString m_name;
ModType m_type = MOD_UNKNOWN;
bool m_from_metadata = false;
/* If the mod has metadata, this will be filled in the constructor, and passed to
* the ModDetails when calling finishResolvingWithDetails */