mirror of
https://github.com/hanzo-cpp/sdk.git
synced 2026-11-20 19:55:32 +00:00
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.
89 lines
2.7 KiB
C++
89 lines
2.7 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.
|
|
*/
|
|
|
|
/*
|
|
* GithubReposOut.h
|
|
*
|
|
*
|
|
*/
|
|
|
|
#ifndef HANZO_MODEL_GithubReposOut_H_
|
|
#define HANZO_MODEL_GithubReposOut_H_
|
|
|
|
#include <boost/optional.hpp>
|
|
|
|
#include "hanzo/ModelBase.h"
|
|
|
|
#include "hanzo/model/GithubRepoView.h"
|
|
#include <cpprest/details/basic_types.h>
|
|
#include <vector>
|
|
|
|
namespace hanzo {
|
|
namespace model {
|
|
|
|
class GithubRepoView;
|
|
|
|
|
|
class GithubReposOut
|
|
: public ModelBase
|
|
{
|
|
public:
|
|
GithubReposOut();
|
|
virtual ~GithubReposOut();
|
|
|
|
/////////////////////////////////////////////
|
|
/// 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;
|
|
|
|
|
|
/////////////////////////////////////////////
|
|
/// GithubReposOut members
|
|
|
|
|
|
/// <summary>
|
|
/// Repos is every repo the installation grants. Never null; [] when none.
|
|
/// </summary>
|
|
std::vector<std::shared_ptr<GithubRepoView>> getRepos() const;
|
|
bool reposIsSet() const;
|
|
void unsetRepos();
|
|
void setRepos(const std::vector<std::shared_ptr<GithubRepoView>>& value);
|
|
|
|
/// <summary>
|
|
/// Unread names the connected accounts this answer could NOT read, so a short list is distinguishable from a complete one. Absent when the answer is whole. The fan-out is per installation, and one account failing used to be dropped in silence: the response stayed 200 and simply carried fewer repositories, erroring only when EVERY account failed. Measured, twice in a row, minutes apart: 1475 repositories, then 1157 — a whole installation missing with nothing in the answer to say so. Anything driven off the list then under-covers and reports success, which is the failure this field ends.
|
|
/// </summary>
|
|
std::vector<utility::string_t> getUnread() const;
|
|
bool unreadIsSet() const;
|
|
void unsetUnread();
|
|
void setUnread(const std::vector<utility::string_t>& value);
|
|
|
|
|
|
protected:
|
|
std::vector<std::shared_ptr<GithubRepoView>> m_Repos;
|
|
bool m_ReposIsSet;
|
|
|
|
std::vector<utility::string_t> m_Unread;
|
|
bool m_UnreadIsSet;
|
|
|
|
};
|
|
|
|
|
|
}
|
|
}
|
|
|
|
#endif /* HANZO_MODEL_GithubReposOut_H_ */
|