mirror of
https://github.com/hanzo-cpp/sdk.git
synced 2026-11-20 19:55:32 +00:00
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.
119 lines
3.3 KiB
C++
119 lines
3.3 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.
|
|
*/
|
|
|
|
/*
|
|
* TeamMessage.h
|
|
*
|
|
*
|
|
*/
|
|
|
|
#ifndef HANZO_MODEL_TeamMessage_H_
|
|
#define HANZO_MODEL_TeamMessage_H_
|
|
|
|
#include <boost/optional.hpp>
|
|
|
|
#include "hanzo/ModelBase.h"
|
|
|
|
#include <cpprest/details/basic_types.h>
|
|
|
|
namespace hanzo {
|
|
namespace model {
|
|
|
|
|
|
|
|
class TeamMessage
|
|
: public ModelBase
|
|
{
|
|
public:
|
|
TeamMessage();
|
|
virtual ~TeamMessage();
|
|
|
|
/////////////////////////////////////////////
|
|
/// 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;
|
|
|
|
|
|
/////////////////////////////////////////////
|
|
/// TeamMessage members
|
|
|
|
|
|
/// <summary>
|
|
/// Author is the team account uuid that wrote it. It is an ACCOUNT and not a display name: what to call somebody is the roster's answer, and copying it onto every message is how the two come to disagree. An agent's messages carry the account derived from its id, so the same field answers for both.
|
|
/// </summary>
|
|
utility::string_t getAuthor() const;
|
|
bool authorIsSet() const;
|
|
void unsetAuthor();
|
|
void setAuthor(const utility::string_t& value);
|
|
|
|
/// <summary>
|
|
/// CreatedOn is unix MILLIseconds, which is what the platform stamps.
|
|
/// </summary>
|
|
int64_t getCreatedOn() const;
|
|
bool createdOnIsSet() const;
|
|
void unsetCreatedOn();
|
|
void setCreatedOn(int64_t value);
|
|
|
|
/// <summary>
|
|
/// ID is the message document's own id.
|
|
/// </summary>
|
|
utility::string_t getId() const;
|
|
bool idIsSet() const;
|
|
void unsetId();
|
|
void setId(const utility::string_t& value);
|
|
|
|
/// <summary>
|
|
/// Room is the room it was said in — the same id the room listing answers with, so a caller holding a message can name its room without a second read.
|
|
/// </summary>
|
|
utility::string_t getRoom() const;
|
|
bool roomIsSet() const;
|
|
void unsetRoom();
|
|
void setRoom(const utility::string_t& value);
|
|
|
|
/// <summary>
|
|
/// Text is the message as PLAIN TEXT. The document stores markup; this is the same `plainText` reduction the agent responder reads a prompt with, so a caller never has to parse the client's markup to know 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_Author;
|
|
bool m_AuthorIsSet;
|
|
|
|
int64_t m_CreatedOn;
|
|
bool m_CreatedOnIsSet;
|
|
|
|
utility::string_t m_Id;
|
|
bool m_IdIsSet;
|
|
|
|
utility::string_t m_Room;
|
|
bool m_RoomIsSet;
|
|
|
|
utility::string_t m_Text;
|
|
bool m_TextIsSet;
|
|
|
|
};
|
|
|
|
|
|
}
|
|
}
|
|
|
|
#endif /* HANZO_MODEL_TeamMessage_H_ */
|