Skip to content

格式化与代码

gRPC .proto ⇄ JSON Schema

Bridge protobuf and JSON Schema definitions.

Runs in your browser
.proto · source
lines: 9chars: 138size: 138 B
JSON Schema · result
lines: 25chars: 375size: 375 B
live

编辑注

Understanding · Two schema languages — one for wire, one for validation.

本深度章节目前仅有英文版本。上方的转换工具支持您的语言;长篇说明文章尚未翻译。

常见问题

Quick answers.

How are protobuf types mapped to JSON Schema?

The converter follows standard proto3 mapping conventions. For example, `string` and `bytes` become `string` types in JSON Schema, while numeric types like `int32` are mapped to `number` or `integer` with range constraints.

Is my API schema sent to a server?

No. The parsing and transformation logic is executed locally using JavaScript in your browser, keeping your protobuf definitions confidential.

Can I convert from JSON Schema back to .proto?

Yes, the tool is bidirectional. You can paste a JSON Schema to generate equivalent protobuf message definitions, though documentation tags and specific gRPC service options may require manual adjustment.

Does it support nested messages and enums?

Yes. The tool recursively processes nested messages, enums, and `oneof` fields into their corresponding `definitions` or `anyOf` representations in JSON Schema.

大家也在搜索

相关工具

More in this room.

查看所有 格式化与代码