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

130 lines
3.4 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.
*/
/*
* Suggestion.h
*
*
*/
#ifndef HANZO_MODEL_Suggestion_H_
#define HANZO_MODEL_Suggestion_H_
#include <boost/optional.hpp>
#include "hanzo/ModelBase.h"
#include <cpprest/details/basic_types.h>
namespace hanzo {
namespace model {
class Suggestion
: public ModelBase
{
public:
Suggestion();
virtual ~Suggestion();
/////////////////////////////////////////////
/// 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;
/////////////////////////////////////////////
/// Suggestion members
/// <summary>
/// Automatable is true when the step names a tool, so the Business AI can do it rather than only describe it.
/// </summary>
bool isAutomatable() const;
bool automatableIsSet() const;
void unsetAutomatable();
void setAutomatable(bool value);
/// <summary>
/// Detail is the step&#39;s own prose — what it asks for.
/// </summary>
utility::string_t getDetail() const;
bool detailIsSet() const;
void unsetDetail();
void setDetail(const utility::string_t& value);
/// <summary>
/// Rationale is why this step is being suggested NOW, written for the person reading it. It explains the ranking, not the step.
/// </summary>
utility::string_t getRationale() const;
bool rationaleIsSet() const;
void unsetRationale();
void setRationale(const utility::string_t& value);
/// <summary>
/// StepID is the checklist step being recommended — the id every step route takes, so a caller can act on the suggestion directly.
/// </summary>
utility::string_t getStepId() const;
bool stepIdIsSet() const;
void unsetStepId();
void setStepId(const utility::string_t& value);
/// <summary>
/// Title is the step&#39;s own one-line quest.
/// </summary>
utility::string_t getTitle() const;
bool titleIsSet() const;
void unsetTitle();
void setTitle(const utility::string_t& value);
/// <summary>
/// Unlocks is how many downstream steps completing this one immediately makes available (its leverage) — the primary ranking key.
/// </summary>
int64_t getUnlocks() const;
bool unlocksIsSet() const;
void unsetUnlocks();
void setUnlocks(int64_t value);
protected:
bool m_Automatable;
bool m_AutomatableIsSet;
utility::string_t m_Detail;
bool m_DetailIsSet;
utility::string_t m_Rationale;
bool m_RationaleIsSet;
utility::string_t m_StepId;
bool m_StepIdIsSet;
utility::string_t m_Title;
bool m_TitleIsSet;
int64_t m_Unlocks;
bool m_UnlocksIsSet;
};
}
}
#endif /* HANZO_MODEL_Suggestion_H_ */