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.