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

111 lines
3.1 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.
*/
/*
* AskAnswer.h
*
*
*/
#ifndef HANZO_MODEL_AskAnswer_H_
#define HANZO_MODEL_AskAnswer_H_
#include <boost/optional.hpp>
#include "hanzo/ModelBase.h"
#include "hanzo/model/Citation.h"
#include <cpprest/details/basic_types.h>
#include <vector>
namespace hanzo {
namespace model {
class Citation;
class AskAnswer
: public ModelBase
{
public:
AskAnswer();
virtual ~AskAnswer();
/////////////////////////////////////////////
/// 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;
/////////////////////////////////////////////
/// AskAnswer members
/// <summary>
/// Answer is the synthesized prose. EMPTY is a real answer here: nothing in the index matched, or synthesis was unavailable — read &#x60;degraded&#x60; and &#x60;citations&#x60; to tell those apart. It is never written without grounding.
/// </summary>
utility::string_t getAnswer() const;
bool answerIsSet() const;
void unsetAnswer();
void setAnswer(const utility::string_t& value);
/// <summary>
/// Citations are the exact regions the answer was grounded on, and they are the point: an answer is checkable only because every claim in it can be read back at a file and line. Present even when Answer is empty.
/// </summary>
std::vector<std::shared_ptr<Citation>> getCitations() const;
bool citationsIsSet() const;
void unsetCitations();
void setCitations(const std::vector<std::shared_ptr<Citation>>& value);
/// <summary>
/// Degraded is true when retrieval worked but no synthesizer was reachable. The citations are still real code, so a caller can answer from them itself; a caller that treats this like an error throws away a usable result.
/// </summary>
bool isDegraded() const;
bool degradedIsSet() const;
void unsetDegraded();
void setDegraded(bool value);
/// <summary>
/// Question is the ask, echoed back.
/// </summary>
utility::string_t getQuestion() const;
bool questionIsSet() const;
void unsetQuestion();
void setQuestion(const utility::string_t& value);
protected:
utility::string_t m_Answer;
bool m_AnswerIsSet;
std::vector<std::shared_ptr<Citation>> m_Citations;
bool m_CitationsIsSet;
bool m_Degraded;
bool m_DegradedIsSet;
utility::string_t m_Question;
bool m_QuestionIsSet;
};
}
}
#endif /* HANZO_MODEL_AskAnswer_H_ */