Files
zeekay 189ce08e51 Regenerate against the document the deployment answers for
The projection these were generated from was a month old and predated the
compute migration, so every one of them described /v1/visor — which the API
serves at zero paths now. That is why a hand-written console client and a
generated one had drifted the same way at the same time.

No /v1/visor path survives here. The word still appears as a source-plane
value and inside gvisor and supervisor, which are not this rename.
2026-09-05 18:07:13 -07:00

119 lines
2.9 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.
*/
/*
* Section.h
*
*
*/
#ifndef HANZO_MODEL_Section_H_
#define HANZO_MODEL_Section_H_
#include <boost/optional.hpp>
#include "hanzo/ModelBase.h"
#include <cpprest/details/basic_types.h>
namespace hanzo {
namespace model {
class Section
: public ModelBase
{
public:
Section();
virtual ~Section();
/////////////////////////////////////////////
/// 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;
/////////////////////////////////////////////
/// Section members
/// <summary>
/// Detail is what this phase of the journey is for, in prose.
/// </summary>
utility::string_t getDetail() const;
bool detailIsSet() const;
void unsetDetail();
void setDetail(const utility::string_t& value);
/// <summary>
/// Enabled is the admin lever. Absent reads as ON, so only an explicit false turns a phase off — and it takes every step filed under it out of the journey, not just the heading.
/// </summary>
bool isEnabled() const;
bool enabledIsSet() const;
void unsetEnabled();
void setEnabled(bool value);
/// <summary>
/// ID is the slug a step&#39;s &#x60;section&#x60; names to file itself under this phase.
/// </summary>
utility::string_t getId() const;
bool idIsSet() const;
void unsetId();
void setId(const utility::string_t& value);
/// <summary>
/// Order places the phase in the journey, ascending. Ties fall back to authoring order, and an omitted order sorts as 0 — ahead of everything.
/// </summary>
int64_t getOrder() const;
bool orderIsSet() const;
void unsetOrder();
void setOrder(int64_t value);
/// <summary>
/// Title is the phase heading a person reads above its steps.
/// </summary>
utility::string_t getTitle() const;
bool titleIsSet() const;
void unsetTitle();
void setTitle(const utility::string_t& value);
protected:
utility::string_t m_Detail;
bool m_DetailIsSet;
bool m_Enabled;
bool m_EnabledIsSet;
utility::string_t m_Id;
bool m_IdIsSet;
int64_t m_Order;
bool m_OrderIsSet;
utility::string_t m_Title;
bool m_TitleIsSet;
};
}
}
#endif /* HANZO_MODEL_Section_H_ */