Generated Computers
Locals: an Apple Silicon engine that runs local LLMs up to 3x faster. A product of Generated Computers.
翻譯準備中
尚未偵測到更新。GitHub 發布版本後會顯示在這裡。
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證The official continuation of LEGO.AsyncAPI.NET from the original author and maintainer. The SDK contains a useful object model for AsyncAPI 3.0 documents in .NET
翻譯準備中
取自儲存庫 README
正在載入完整 README。
檢視完整 README ↗AsyncAPI.NET provides a .NET object model for AsyncAPI documents, JSON/YAML readers and writers, and protocol bindings.
It supports AsyncAPI 2.x and 3.x. V2 documents are upgraded to the V3-shaped model when read and can be written back as V2. Serialization currently emits 2.6 or 3.1.0; the V3 selector is still named AsyncApiVersion.AsyncApi3_0.
See the documentation site for guides and examples, or the changelog for release notes.
Install the core model and serializers, plus the readers for JSON/YAML input:
dotnet add package ByteBard.AsyncAPI.NET
dotnet add package ByteBard.AsyncAPI.NET.Readers
For protocol bindings, also install:
dotnet add package ByteBard.AsyncAPI.NET.Bindings
Binding readers require explicit registration; see protocol bindings.
Parse YAML, check diagnostics, and write JSON (C# 11 or later):
using System;
using ByteBard.AsyncAPI;
using ByteBard.AsyncAPI.Models;
using ByteBard.AsyncAPI.Readers;
var source = """
asyncapi: 3.1.0
info:
title: Example API
version: 1.0.0
channels: {}
""";
var document = new AsyncApiStringReader().Read(source, out var diagnostics);
foreach (var error in diagnostics.Errors)
Console.Error.WriteLine($"Error at {error.Pointer}: {error.Message}");
foreach (var warning in diagnostics.Warnings)
Console.Error.WriteLine($"Warning at {warning.Pointer}: {warning.Message}");
if (diagnostics.Errors.Count > 0)
return;
Console.WriteLine(document.SerializeAsJson(AsyncApiVersion.AsyncApi3_0));
Contributions and suggestions are welcome. See CONTRIBUTING.md and the documentation development instructions.