Files
zeekay 645325a641 regenerate from cloud 939b09d4
The projection was 113 commits behind the document it claims to describe, and
`generate.py --all --check` reported every one of the thirteen clients DRIFTED —
the same +19 models in each, because they all fell behind the same emission.

Regenerated in place from hanzo-inc/cloud openapi.yaml at 939b09d4
(sha256 087024f6…), which is the only description of this API that cannot name a
route the binary does not serve. `--check` is clean across all thirteen after.

.spec-lock moved with the code. The generator READS that file and never writes
it — hanzoai/ci`s lane does — so a hand run leaves every lock naming the previous
document. A lock that disagrees with the tree beside it is worse than no lock:
the next `--check` without `--spec` fetches what production serves, compares it
to a digest that was already wrong, and reports drift that is really staleness.
2026-08-24 23:32:53 -07:00

108 lines
3.0 KiB
C++

/**
* Hanzo Cloud API
* The Hanzo Cloud API as a customer calls it: every operation under /v1/ except the operator's admin product, relay routes, legacy spellings and capabilities still reached by flag. Tagged by product: the first path segment after /v1/.
*
* The version of the OpenAPI document: v1
*
* NOTE: This class is auto generated by OpenAPI-Generator 7.14.0.
* https://openapi-generator.tech
* Do not edit the class manually.
*/
/*
* Account.h
*
*
*/
#ifndef HANZO_MODEL_Account_H_
#define HANZO_MODEL_Account_H_
#include <boost/optional.hpp>
#include "hanzo/ModelBase.h"
#include <cpprest/details/basic_types.h>
namespace hanzo {
namespace model {
class Account
: public ModelBase
{
public:
Account();
virtual ~Account();
/////////////////////////////////////////////
/// ModelBase overrides
void validate() override;
web::json::value toJson() const override;
bool fromJson(const web::json::value& json) override;
void toMultipart(std::shared_ptr<MultipartFormData> multipart, const utility::string_t& namePrefix) const override;
bool fromMultiPart(std::shared_ptr<MultipartFormData> multipart, const utility::string_t& namePrefix) override;
/////////////////////////////////////////////
/// Account members
/// <summary>
/// Name is the account&#39;s human name, for a statement&#39;s line label.
/// </summary>
utility::string_t getName() const;
bool nameIsSet() const;
void unsetName();
void setName(const utility::string_t& value);
/// <summary>
/// Number is the posting key every voucher leg, rule and report references — stable, and the reason the chart is a fixed value rather than a table anybody can edit. It looks numeric and is a string: \&quot;1000\&quot; sorts and compares as text.
/// </summary>
utility::string_t getNumber() const;
bool numberIsSet() const;
void unsetnumber();
void setNumber(const utility::string_t& value);
/// <summary>
/// Party marks the account as carrying a SUBLEDGER — receivable is money owed to us, payable money we owe — so a leg posted here also writes a payment-ledger row against a counterparty. Absent means no subledger: a bank, wallet, revenue or cost account tracks no counterparty at all.
/// </summary>
utility::string_t getParty() const;
bool partyIsSet() const;
void unsetParty();
void setParty(const utility::string_t& value);
/// <summary>
/// Type is the account&#39;s fundamental class, which is also its NORMAL balance side: asset and expense are debit-normal, liability, income and equity credit-normal.
/// </summary>
utility::string_t getType() const;
bool typeIsSet() const;
void unsetType();
void setType(const utility::string_t& value);
protected:
utility::string_t m_Name;
bool m_NameIsSet;
utility::string_t m_number;
bool m_numberIsSet;
utility::string_t m_Party;
bool m_PartyIsSet;
utility::string_t m_Type;
bool m_TypeIsSet;
};
}
}
#endif /* HANZO_MODEL_Account_H_ */