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

104 lines
4.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.
*/
/*
* LspApi.h
*
*
*/
#ifndef HANZO_API_LspApi_H_
#define HANZO_API_LspApi_H_
#include "hanzo/ApiClient.h"
#include "hanzo/model/Answer.h"
#include "hanzo/model/Query.h"
#include <boost/optional.hpp>
namespace hanzo {
namespace api {
using namespace hanzo::model;
class LspApi
{
public:
explicit LspApi( std::shared_ptr<const ApiClient> apiClient );
virtual ~LspApi();
/// <summary>
/// Offers the candidates a language server has at a position, typed and resolved through the repository&#39;s dependencies rather than guessed from text.
/// </summary>
/// <remarks>
/// Offers the candidates a language server has at a position, typed and resolved through the repository&#39;s dependencies rather than guessed from text.
/// </remarks>
/// <param name="query"></param>
pplx::task<std::shared_ptr<Answer>> postLspComplete(
std::shared_ptr<Query> query
) const;
/// <summary>
/// Reports every problem the language server finds in one file — compile errors, type errors and lints, each with its span and its severity (1 error, 2 warning, 3 information, 4 hint).
/// </summary>
/// <remarks>
/// Reports every problem the language server finds in one file — compile errors, type errors and lints, each with its span and its severity (1 error, 2 warning, 3 information, 4 hint). The position is ignored.
/// </remarks>
/// <param name="query"></param>
pplx::task<std::shared_ptr<Answer>> postLspDiagnostics(
std::shared_ptr<Query> query
) const;
/// <summary>
/// Renders the type and documentation of the symbol at a position, as the language server itself renders it.
/// </summary>
/// <remarks>
/// Renders the type and documentation of the symbol at a position, as the language server itself renders it. Positions are the LSP&#39;s: line and character are 0-BASED and character counts UTF-16 code units, so an editor&#39;s 1-based line must have 1 subtracted before it is sent. The repository is named by slug and is always one in the caller&#39;s own org; rev pins a branch, tag or commit sha, and empty means the default branch.
/// </remarks>
/// <param name="query"></param>
pplx::task<std::shared_ptr<Answer>> postLspHover(
std::shared_ptr<Query> query
) const;
/// <summary>
/// Finds where a symbol lives: its definition, its references, its type or its implementations, chosen by relation (definition, reference, type, implementation — empty means definition).
/// </summary>
/// <remarks>
/// Finds where a symbol lives: its definition, its references, its type or its implementations, chosen by relation (definition, reference, type, implementation — empty means definition). It resolves THROUGH dependencies. An answer whose external flag is set left the repository, and its path is then the module coordinate it landed in — which is the question a static index cannot answer and this service exists for.
/// </remarks>
/// <param name="query"></param>
pplx::task<std::shared_ptr<Answer>> postLspLocate(
std::shared_ptr<Query> query
) const;
/// <summary>
/// Outlines one file: every declaration in it, with its kind and its span.
/// </summary>
/// <remarks>
/// Outlines one file: every declaration in it, with its kind and its span. The position is ignored — the answer is the whole file.
/// </remarks>
/// <param name="query"></param>
pplx::task<std::shared_ptr<Answer>> postLspSymbols(
std::shared_ptr<Query> query
) const;
protected:
std::shared_ptr<const ApiClient> m_ApiClient;
};
}
}
#endif /* HANZO_API_LspApi_H_ */