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

174 lines
6.8 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.
*/
/*
* InboxView.h
*
*
*/
#ifndef HANZO_MODEL_InboxView_H_
#define HANZO_MODEL_InboxView_H_
#include <boost/optional.hpp>
#include "hanzo/ModelBase.h"
#include <cpprest/details/basic_types.h>
namespace hanzo {
namespace model {
class InboxView
: public ModelBase
{
public:
InboxView();
virtual ~InboxView();
/////////////////////////////////////////////
/// 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;
/////////////////////////////////////////////
/// InboxView members
/// <summary>
/// Account is the lowercased external id of the org&#39;s connected account on that transport: the Discord guild id, the Slack team id, the Teams AAD tenant id, or the bound Telegram chat id. Informational only — the gate keys on (org, channel), never on the account.
/// </summary>
utility::string_t getAccount() const;
bool accountIsSet() const;
void unsetAccount();
void setAccount(const utility::string_t& value);
/// <summary>
/// Channel is the transport this message arrived on — discord, slack, teams or telegram — and the &#x60;:channel&#x60; segment to reply through.
/// </summary>
utility::string_t getChannel() const;
bool channelIsSet() const;
void unsetChannel();
void setChannel(const utility::string_t& value);
/// <summary>
/// CreatedAt is Unix SECONDS, stamped by the ingest goroutine when the message was accepted — not the transport&#39;s own send time. Rows are dropped 30 days after it.
/// </summary>
int64_t getCreatedAt() const;
bool createdAtIsSet() const;
void unsetCreatedAt();
void setCreatedAt(int64_t value);
/// <summary>
/// ID is the store&#39;s row id, assigned on insert — SERVER-SET, and the cursor: pass a page&#39;s last id back as &#x60;since&#x60;. It rises with arrival order but is not contiguous, because one sequence is shared by every org in the store and a caller reads only its own rows.
/// </summary>
int64_t getId() const;
bool idIsSet() const;
void unsetId();
void setId(int64_t value);
/// <summary>
/// ReplyTo is the transport&#39;s reply target for this message: Slack&#39;s thread_ts, or the Telegram message id it arrived as. Send it back as the body&#39;s &#x60;replyTo&#x60; to answer in the SAME thread. Empty means the transport reported none — a top-level Slack message, and every Discord and Teams message, since neither carries one — and a reply then lands at the top level of the room.
/// </summary>
utility::string_t getReplyTo() const;
bool replyToIsSet() const;
void unsetReplyTo();
void setReplyTo(const utility::string_t& value);
/// <summary>
/// RoomID is the conversation on the ORIGINATING transport, and the value to send back as &#x60;room.id&#x60;: a Discord channel snowflake, a Slack conversation id (D… IM, C… public channel, G… private or mpim), a Teams conversation id (19:…@thread.… for a channel or group chat, a:… for a personal chat), or a Telegram chat id in decimal (negative for a group, positive for a DM). It is stable for the life of the room, so every message from one conversation carries the same value.
/// </summary>
utility::string_t getRoomId() const;
bool roomIdIsSet() const;
void unsetRoomId();
void setRoomId(const utility::string_t& value);
/// <summary>
/// RoomKind is how ingest classified the room: \&quot;dm\&quot;, \&quot;group\&quot; or \&quot;thread\&quot;. It decides which policy gated the message — dmPolicy for \&quot;dm\&quot;, groupPolicy for BOTH \&quot;group\&quot; and \&quot;thread\&quot;. Only Slack ever reports \&quot;thread\&quot;; Telegram&#39;s reply-to id becomes ReplyTo instead, and Discord&#39;s ingress is guild-scoped so its rooms are always \&quot;group\&quot;.
/// </summary>
utility::string_t getRoomKind() const;
bool roomKindIsSet() const;
void unsetRoomKind();
void setRoomKind(const utility::string_t& value);
/// <summary>
/// Sender is the TRANSPORT-NATIVE user id of whoever wrote the message — a Discord member.user.id, a Slack U… user id, a Teams aadObjectId (falling back to from.id), a Telegram from.id in decimal. Stable per person per transport, and the identity the gate keys on: an allow entry, an access-group member and a pairing approval all name exactly this value.
/// </summary>
utility::string_t getSender() const;
bool senderIsSet() const;
void unsetSender();
void setSender(const utility::string_t& value);
/// <summary>
/// SenderUser is the HANZO account subject that chat identity is linked to, resolved at ingest through the org&#39;s user link. Best-effort and omitted when absent: a person who never linked their chat account — or a link store that could not be read — leaves it empty and is never blocked for it.
/// </summary>
utility::string_t getSenderUser() const;
bool senderUserIsSet() const;
void unsetSenderUser();
void setSenderUser(const utility::string_t& value);
/// <summary>
/// Text is the body as the transport delivered it, with the bot mention already stripped by the ingress adapter (on Discord it is the /hanzo prompt argument, since that ingress is slash commands only), truncated to 8 KiB on store. Inbound attachments are not stored — this is the whole of what was said.
/// </summary>
utility::string_t getText() const;
bool textIsSet() const;
void unsetText();
void setText(const utility::string_t& value);
protected:
utility::string_t m_Account;
bool m_AccountIsSet;
utility::string_t m_Channel;
bool m_ChannelIsSet;
int64_t m_CreatedAt;
bool m_CreatedAtIsSet;
int64_t m_Id;
bool m_IdIsSet;
utility::string_t m_ReplyTo;
bool m_ReplyToIsSet;
utility::string_t m_RoomId;
bool m_RoomIdIsSet;
utility::string_t m_RoomKind;
bool m_RoomKindIsSet;
utility::string_t m_Sender;
bool m_SenderIsSet;
utility::string_t m_SenderUser;
bool m_SenderUserIsSet;
utility::string_t m_Text;
bool m_TextIsSet;
};
}
}
#endif /* HANZO_MODEL_InboxView_H_ */