rpl

KO | EN

gitlite — search

#pytorch #css #codex #http #computer-vision #android #cli #editor #tailwindcss #cloud-native

(★ 12)

Declarative language for describing models and metadata.

파일 탐색기

ZIP 다운로드

- ffi-and-wasm-plugins.md
- generated-plugin-api.md
- - 01-basic-model.rpl
  - 02-package-and-imports.rpl
  - 03-model-methods.rpl
  - 04-field-methods.rpl
- - 01-comment-group-ignore.rpl
  - 02-groups-for-derived-models.rpl
  - 03-selective-ignore.rpl
  - 04-derived-command-models.rpl
  - README.md
- - 01-string-and-number-validation.rpl
  - 02-length-time-and-hash.rpl
  - 03-collections-and-optional-values.rpl
  - 04-security-profile.rpl
  - README.md
- - 01-user-storage.rpl
  - 02-sql-ignore-and-defaults.rpl
  - 03-sqlite-storage.rpl
  - 04-composite-primary-key.rpl
  - 05-json-and-custom-columns.rpl
  - 06-enum-columns.rpl
  - README.md
- - 01-session-cache.rpl
  - 02-redis-ignore-fields.rpl
  - 03-composite-cache-key.rpl
  - 04-optional-and-fallback-key.rpl
  - 05-enum-values.rpl
  - README.md
- - 01-basic-service.rpl
  - 02-classic-custom-methods.rpl
  - 03-model-bound-methods-by-model.rpl
  - 04-model-bound-methods-by-id.rpl
  - 05-inside-and-field-methods.rpl
  - 06-nested-messages-and-ignore.rpl
  - 07-method-subject-overrides.rpl
  - 08-enum-fields.rpl
  - README.md
- - extensions.rpl
  - main.rpl
  - profile.rpl
- - main.rpl
  - shared.rpl
- - 01-user-store.rpl
  - 02-sparse-profile-store.rpl
  - 03-search-sort-and-defaults.rpl
  - README.md
- - 01-os-bin-service.rpl
  - 02-http-service.rpl
  - 03-unix-socket-service.rpl
  - 04-nats-service.rpl
  - 05-kafka-service.rpl
  - 06-websocket-service.rpl
  - 07-multi-adapter-service.rpl
  - 08-model-and-id-subjects.rpl
  - 09-method-only-adapters.rpl
  - README.md
- - 01-rust-server-all-clients.rpl
  - 02-c-server-selected-clients.rpl
  - 03-enum-wire-values.rpl
  - README.md
- - 01-rust-component.rpl
  - 02-contract-only.rpl
  - 03-enum-wire-values.rpl
  - README.md
- - 01-basic-enum.rpl
  - 02-go-types.rpl
  - 03-plugin-apis.rpl
  - README.md
- - 01-expression-arena.rpl
  - 02-json-like-arena.rpl
  - README.md
- - 01-model-defaults.rpl
  - 02-exact-field-tags.rpl
  - 03-naming-modes.rpl
  - README.md
- - extensions.rpl
  - main.rpl
  - README.md
  - realtime.rpl
  - support.rpl
- - README.md
- README.md
- - go.mod
- - main.go
- go.mod
- - go.mod
  - go.sum
  - README.md
- README.md
.gitignore
LICENSE
Makefile
README.md

# CDN으로 사용하기

jsDelivr

jsDelivr는 공개 GitHub 리포지토리를 별도 설정 없이 CDN으로 즉시 서빙합니다. 버전과 파일을 고르면 웹페이지에 바로 붙일 수 있는 링크와 예시 코드가 만들어집니다.

버전

파일

링크

예시

# 프로젝트 배지

Release 바로가기
License 바로가기
Go 바로가기
VS Code 바로가기

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

RPL is a declarative schema language, compiler, extensible code-generation
runtime, and developer toolchain. It turns compact `.rpl` files into typed Go
models and the infrastructure around them: validation, SQL, MongoDB, Redis,
protobuf/gRPC, multi-transport adapters, documentation, and editor tooling.

The project includes:

- the RPL language parser, semantic analyzer, formatter, and Go target;
- a CLI for projects, generation, formatting, imports, docs, and attrs;
- a newline-oriented JSON runtime used by editor integrations;
- a public Go SDK for writing generator attrs;
- eleven bundled `rpl:*` attrs;
- a VS Code extension with diagnostics, completion, CodeLens, navigation,
  tasks, and toolchain management;
- examples, integration fixtures, and release builds for six OS/architecture
  combinations.

> Current release: **RPL 0.7.3**. The repository includes the Go target
> (`target(lang: golang)`) and the artifact-only FFI target
> (`target(lang: ffi)`).

## Table of contents

- [Why RPL](#why-rpl)
- [How it works](#how-it-works)
- [Installation](#installation)
- [Quick start](#quick-start)
- [Language guide](#language-guide)
- [Built-in attrs](#built-in-attrs)
- [CLI reference](#cli-reference)
- [Project configuration](#project-configuration)
- [Runtime API and attr SDK](#runtime-api-and-attr-sdk)
- [VS Code extension](#vs-code-extension)
- [Examples](#examples)
- [Repository architecture](#repository-architecture)
- [Development and testing](#development-and-testing)
- [Release builds](#release-builds)
- [Troubleshooting](#troubleshooting)
- [License](#license)

## Why RPL

Application models are usually repeated across structs, validators, database
queries, protobuf messages, clients, servers, and documentation. Those copies
drift. RPL keeps the model and its intent in one schema while leaving generated
Go code explicit, typed, and inspectable.

RPL is designed around a few principles:

1. **The schema stays small.** Models, fields, methods, defaults, imports, and
   generator metadata use a compact language.
2. **Generators are explicit.** A schema lists the attrs it depends on and
   applies them where they matter.
3. **Attrs are independent processes.** Built-in and local generators use a
   versioned SDK protocol instead of being hard-coded into the parser.
4. **Generated code is ordinary Go.** The output can be read, tested, and used
   without a special runtime embedded in the application.
5. **Diagnostics come from the real compiler.** The CLI and VS Code extension
   share parser, semantic analysis, formatting, attr discovery, and type
   catalog behavior.
6. **Generation is deterministic.** RPL tracks generated files and removes
   stale sidecars when schema capabilities change.

## How it works

```text
                         ┌──────────────────────┐
 .rpl files ───────────► │ parser + semantic    │
 imports / package       │ analysis + formatter │
                         └──────────┬───────────┘
                                    │ normalized schema + context
                                    ▼
                         ┌──────────────────────┐
 .rpl/config.xml ──────► │ attr discovery and   │ ◄──── bundled / local attrs
                         │ capability planning   │       rpl:sql, rpl:grpc, ...
                         └──────────┬───────────┘
                                    │ generated file claims
                                    ▼
                         ┌──────────────────────┐
                         │ Go target + attr     │
                         │ generators           │
                         └──────────┬───────────┘
                                    │
                                    ▼
                         models, validators, stores,
                         protobuf, clients, servers, docs
```

The core compiler owns parsing, cross-file resolution, model groups, target
types, diagnostics, and generated-file coordination. Attrs contribute analysis,
documentation, and generated files at model or file scope. Conflicting Go file
claims are detected before output is written.

## Installation

### Download a release

Open [GitHub Releases](https://github.com/rp1s/rpl/releases/latest) and choose
the archive for your platform:

| Platform | Asset |
| --- | --- |
| macOS Apple Silicon | `rpl-v0.7.3-darwin-arm64.tar.gz` |
| macOS Intel | `rpl-v0.7.3-darwin-amd64.tar.gz` |
| Linux x86-64 | `rpl-v0.7.3-linux-amd64.tar.gz` |
| Linux ARM64 | `rpl-v0.7.3-linux-arm64.tar.gz` |
| Windows x86-64 | `rpl-v0.7.3-windows-amd64.zip` |
| Windows ARM64 | `rpl-v0.7.3-windows-arm64.zip` |

Every CLI archive contains:

```text
rpl-v0.7.3-<os>-<arch>/
├── rpl or rpl.exe
├── .rpl/
│   ├── attrs/
│   │   ├── rpl_std/
│   │   ├── rpl_validate/
│   │   ├── rpl_sql/
│   │   ├── rpl_mongodb/
│   │   ├── rpl_redis/
│   │   ├── rpl_grpc/
│   │   ├── rpl_transport/
│   │   ├── rpl_ffi/
│   │   ├── rpl_wasm/
│   │   ├── rpl_parser/
│   │   └── rpl_json/
│   └── sdk/
│       ├── go.mod
│       └── pkg/sdk/
├── README.md
└── LICENSE
```

Keep the executable and its `.rpl` directory together. RPL discovers bundled
attrs relative to the executable. The SDK sidecar lets `rpl attr init` create a
self-contained Go module that can compile outside the RPL source repository.

Verify the download against `checksums.txt`, then run:

```bash
./rpl help
./rpl attr list
```

On Unix, place the extracted directory somewhere stable and add or symlink the
executable into a directory on `PATH`. On Windows, add the extracted directory
to `PATH` without separating `rpl.exe` from `.rpl`.

### Build from source

Requirements:

- Go 1.25 or newer;
- `make` for the repository shortcuts;
- Node.js only when building the VS Code extension;
- `protoc` and Go protobuf tools when working on protobuf generation internals.

```bash
git clone https://github.com/rp1s/rpl.git
cd rpl
make build-host
```

The host build is created under:

```text
build/<goos>-<goarch>/rpl
build/<goos>-<goarch>/.rpl/attrs/
build/<goos>-<goarch>/.rpl/sdk/
```

To build and install into `~/.local/bin` together with bundled attrs:

```bash
make install
```

The installer copies the CLI, bundled attrs, and attr SDK together, then adds
`~/.local/bin` to the detected shell profile if necessary.

## Quick start

### 1. Create a project

```bash
rpl init hello-rpl
cd hello-rpl
```

`rpl init` creates missing files but keeps existing files unchanged:

```text
hello-rpl/
├── .rpl/
│   ├── config.xml
│   └── attrs/
├── src/
│   └── main.rpl
└── README.md
```

### 2. Define a schema

```rpl
package account

target(lang: golang)

import (
    "time"
)

attrs (
    "rpl:sql"
    "rpl:validate"
)

@sql(db: "postgres", table: "users")
model User {
    Id int64 @sql(column: "id", primaryKey: true)
    Email string @validate(email) @sql(unique: true, index: true)
    Name string = "anonymous" @validate(min: 2, max: 64)
    CreatedAt time.Time @sql(default: "now") @validate(past)
    UpdatedAt time.Time? @sql(default: "now", updatedAt: true)
}
```

### 3. Format and complete imports

```bash
rpl auto set import src/main.rpl
rpl fmt src/main.rpl
```

### 4. Generate code

```bash
rpl run src/main.rpl out models
```

The exact output depends on enabled attrs. For the schema above it includes the
base Go model, validation helpers, SQL DDL, scanners, typed columns, CRUD/query
helpers, and a `Store` abstraction.

### 5. Generate schema documentation

```bash
rpl docs src/main.rpl
```

## Language guide

### Package and target

`package` groups multiple `.rpl` files into one logical package. It is optional
for a single-file schema. `target` selects the output language:

```rpl
package billing

target(lang: golang)
```

When a package contains several files, the compiler resolves them together and
keeps package-level target ownership consistent.

### Imports

The same `import` block can reference Go packages and other RPL files:

```rpl
import (
    "time"
    http "net/http"
    "shared.rpl"
)
```

Go imports make external types such as `time.Time` and `http.Request`
available to the schema and generated package. RPL imports make models from
another schema file available for resolution.

Imported Go structs and named types retain their original identity, methods,
and package ownership. They work directly in fields, lists, optional values,
and method signatures; `type Local domain.Type` creates a generated Go alias.
See [`examples/12-enums/02-go-types.rpl`](examples/12-enums/02-go-types.rpl).

### Enums

Enums use `uint` by default and may select another unsigned representation:

```rpl
enum Status {
    Unknown
    Pending (string, int) = "ожидает", 4
    Failed string
}

enum WireCode: uint8 {
    OK
    Retry
}
```

The Go target generates prefixed constants, `String`, `IsValid`, `Values`, and
`Parse` helpers. A type or tuple after a variant produces a Rust-like companion
value API (`StatusValue`, `NewStatusPending`, `AsPending`). Tuple defaults are
positional and must match their payload count; the first string default becomes
the `String()` label. See
[`examples/12-enums`](examples/12-enums) and the complete
[`enum-go-interop`](examples/projects/enum-go-interop) project.

### Attr declarations

Before using a generator namespace, declare its runtime identifier:

```rpl
attrs (
    "rpl:std"
    "rpl:validate"
    "rpl:sql"
)
```

The compiler discovers each manifest and executable, asks the attr for its
specification and capabilities, validates attr arguments, runs analysis, and
collects generated files.

### Models and fields

```rpl
model User {
    Id int64
    Name string
    Active bool = true
    Nickname string?
    Tags []string
}
```

- field names use exported Go-style identifiers;
- `?` marks an optional value;
- `[]T` represents a repeated value;
- `= expression` declares a default expression;
- model names can be used as field types;
- imported Go types can be referenced by package alias.
- enums generate compact unsigned tags and optional typed variant data.

RPL understands common Go scalar types, `[]byte`, `time.Time`, model types, and
external imported types. The target type catalog is also exposed to editor
completion through the runtime API.

### Attr syntax

Attrs can be written inline:

```rpl
Email string @validate(email) @sql(unique: true)
```

or in a block when several annotations need to stay readable:

```rpl
Email string
{
    @comment("Public login address.")
    @validate(email: true, minLen: 6, maxLen: 160)
    @sql(unique: true, index: true)
}
```

Attrs can apply to models, fields, and methods. Their allowed arguments and
value types come from the runtime `AttrSpec`, so CLI and editor validation stay
aligned with the actual generator.

### Model methods

```rpl
model User {
    FirstName string
    LastName string
}

func User {
    func DisplayName return (string)
    func IsNamed return (bool)
}
```

Methods may also be declared inside a model and can accept parameters:

```rpl
model User {
    Name string

func Greeting (prefix string) return (string)
}
```

### Field methods

```rpl
model User {
    Email string
}

func User.Email {
    func Domain return (string)
    func Normalized return (string)
}
```

Field-bound and model-bound methods can be consumed by transport attrs. gRPC
also supports inspecting exported methods of imported Go types for explicit
inside-field exposure.

### Groups and derived models

`@group` creates reusable projections such as request, public, or private
models:

```rpl
attrs (
    "rpl:std"
)

model User {
    Name string @group("req")
    Age int @group("req")
    Bio string @group("public")
}

model AuditEntry {
    Actor UserReq
    Snapshot UserPublic
}
```

### Ignore rules

Use a generator-specific flag or the standard `@ignore` attr:

```rpl
Secret string @ignore("grpc", "sql", "redis")
DebugState string @redis(ignore: true)
InternalFlags string @grpc(ignore: true)
```

### Multi-file packages

Models may be split across several `.rpl` files sharing the same package. Run
generation from the package entry file; the compiler finds related package
files, resolves cross-file types, and generates one coordinated output tree.

See [`examples/06-multifile`](examples/06-multifile) and
[`examples/07-imports`](examples/07-imports).

## Built-in attrs

| Runtime | Version | Main responsibility |
| --- | ---: | --- |
| `rpl:std` | 1.0.0 | comments, groups, and cross-generator ignore metadata |
| `rpl:validate` | 1.1.0 | field validation, UUID/regexp rules, and sensitive/hash helpers |
| `rpl:sql` | 1.2.0 | PostgreSQL/SQLite DDL, scans, CRUD, typed queries, stores |
| `rpl:mongodb` | 1.1.0 | BSON adapters, compound indexes, search/sort metadata, CRUD helpers |
| `rpl:redis` | 1.1.0 | Redis keys, hash storage, custom names, typed defaults, TTL |
| `rpl:grpc` | 1.0.0 | `.proto`, protobuf Go, gRPC services, clients, conversions |
| `rpl:transport` | 2.1.0 | shared service contracts, routing defaults, and six delivery adapters |
| `rpl:ffi` | 1.1.0 | stable C ABI, C/Rust servers, Go/Python/C/Rust clients, cgo-free `go:purego` client |
| `rpl:wasm` | 0.1.0 | WIT contract, Rust Component guest, typed Wasmtime host, deny-by-default manifest |
| `rpl:parser` | 0.1.0 | longest-match lexer, PEG parser, flat arena AST with uint32 node/edge indexes |
| `rpl:json` | 0.1.0 | validated `encoding/json` tags on primary generated Go models |

### `rpl:std`

Standard metadata understood across the toolchain:

- `@comment("text")` attaches documentation to a model or field;
- `@group("name")` includes a field in a derived projection;
- `@ignore("attr", ...)` excludes a field from selected generators.

### `rpl:validate`

Field validation arguments:

| Argument | Purpose |
| --- | --- |
| `required` | reject empty strings/collections, absent optionals, and zero timestamps |
| `min`, `max` | numeric or comparable range constraints |
| `minLen`, `maxLen` | string/collection length constraints |
| `email` | email format validation |
| `phone` | phone format validation |
| `url` | URL validation |
| `uuid` | canonical UUID validation for strings and string lists |
| `pattern` | custom regular expression, checked during schema analysis |
| `past` | require a timestamp in the past |
| `hash` | mark a sensitive value and generate hash-oriented helpers |

Example:

```rpl
model Signup {
    ID string @validate(required: true, uuid: true)
    Name string @validate(required: true, min: 2, max: 32, pattern: "^[A-Za-z ]+$")
    Email string @validate(required: true, email: true)
    Password string @validate(minLen: 8, maxLen: 128, hash: "password")
}
```

### `rpl:sql`

Model arguments:

- `db`: `postgres` (default) or `sqlite`;
- `table`: explicit table name;
- `orderBy`: generated default order, by field or SQL column name.

Field arguments:

- `column`, `primaryKey`, `unique`, `index`, `search`;
- `default`, `updatedAt`, `ignore`.

The generator validates and quotes identifiers, supports composite primary
keys, excludes keys from `UPDATE SET`, chooses a valid upsert conflict target,
and handles SQLite pagination. Generated APIs include DDL initialization,
scanners, CRUD/query functions, typed `Column` values, `Where`/`And`, an
`Executor` interface compatible with `*sql.DB` and `*sql.Tx`, and `NewStore`.

```go
store := usersql.NewStore(db)
if err := store.Init(ctx); err != nil {
    return err
}

user, err := store.Get(ctx,
    usersql.Where(usersql.ColumnEmail, email),
)
```

`Init` is a bootstrap helper using `CREATE TABLE/INDEX IF NOT EXISTS`; it is not
a destructive migration engine. More details are in
[`src/attrs/rpl:sql/README.md`](src/attrs/rpl:sql/README.md).

### `rpl:mongodb`

Model arguments: `db`, `collection`.

Field arguments: `name`, `index`, `indexGroup`, `indexOrder`, `unique`,
`sparse`, `search`, `sort`, `objectId`, `omitempty`, `default`, `updatedAt`,
and `ignore`. Fields sharing an `indexGroup` form one compound index;
`indexOrder` is `1` or `-1`.

The output includes collection constants, index definitions, BSON conversion,
metadata, CRUD/query helpers, search filters, sort fields, ObjectID handling,
and update timestamp behavior.

### `rpl:redis`

Model arguments: `db`, `table`, `ttl`.

Field arguments: `name`, `unique`, `default`, `ignore`.

The generator produces model key conventions, hash serialization helpers,
unique-key metadata, defaults, and expiration-aware storage helpers.
Defaults are type-checked and applied when a Redis hash key is absent. `name`
provides a stable stored hash name independent of the RPL field name.

### `rpl:grpc`

`@grpc()` generates protobuf definitions, protobuf Go code, typed gRPC
services, clients, servers, and conversion helpers. It supports:

- ordinary model services;
- custom model methods;
- model-bound calls with `@grpc.Model()` or `model: true`;
- identity fields with `@grpc.id()`;
- subject binding;
- ignored fields;
- explicit inside fields/methods through `@grpc.Inside()` or `mode: "inside"`;
- inspection of exported methods on imported Go types.

Generated sidecar files are tracked and removed if gRPC is later removed from
the schema.

### `rpl:transport`

Transport 2 generates one service contract with any combination of:

```rpl
@transport(os.bin)
@transport(http, httpPath: "/api/users", brokerPrefix: "acme.users", kafkaGroup: "acme-users-rpc")
@transport(unix)
@transport(nats)
@transport(kafka)
@transport(websocket)
model User {
    Id int @transport.id()
    Name string
    func Health return (string)
    func Changed return (string) @transport(kafka)
}
```

Model-level modes share CRUD and methods without an explicit mode. A
method-level mode restricts that operation to one adapter while retaining one
business interface. Generated output includes mode-aware dispatch, typed
clients, request/response types, and adapter lifecycle helpers.

HTTP uses `net/http`; Unix uses domain sockets. NATS, Kafka, and WebSocket expose
small integration interfaces so applications can choose and version their own
client libraries. Kafka's bridge explicitly owns correlation IDs and reply
topics because Kafka is not inherently request/reply.

`httpPath`, `brokerPrefix`, and `kafkaGroup` move deployment routing defaults
into the schema while generated constructors still permit runtime overrides.

Identity and model-bound semantics continue to use `@transport.id()` and
`@transport.Model()`. Omitting a mode remains equivalent to `os.bin`.
See the complete [`transport attr guide`](src/attrs/rpl:transport/README.md) and
[`multi-transport project`](examples/projects/process-service/README.md).

### `rpl:ffi`

FFI turns model methods into a versioned in-process ABI:

```rpl
target(lang: ffi)

@ffi(server: "rust", clients: "go,go:purego,python,c,rust", library: "calculator")
model CalculatorService {
    func Add (left int64, right int64) return (int64)
    func Stats return (int64, float64)
}
```

`target(lang: ffi)` is artifact-only: it suppresses the compiler's host
`model.gen.go`. A selected Go client still gets its own self-contained binding
under `ffi/go`; use `target(lang: golang)` only when a separate Go domain model
is intentionally required alongside the ABI.

The generated C header defines borrowed views, owned buffers, status codes,
the model layout, service callback vtable, and stable call/free symbols. Method
payloads use UTF-8 JSON so lists, optional values, nested models, and future
fields do not depend on a language-specific object layout.

Rust servers receive typed request/response structures and an `FFIService`
trait. C servers implement the generated callback vtable. `clients: "go"`
emits the normal cgo Go bridge, while `clients: "go:purego"` emits the cgo-free
[`purego`](https://github.com/ebitengine/purego) dynamic loader. Use
`clients: "go,go:purego"` when both Go modes are useful. Python uses `ctypes`;
C and Rust clients call the same header contract. Build the pure-Go client with
`CGO_ENABLED=0 -tags rpl_ffi_purego`.

See the complete [`FFI attr guide`](src/attrs/rpl:ffi/README.md) and
[`FFI examples`](examples/10-ffi/README.md).

### `rpl:wasm`

WASM is a separate application-plugin boundary built on WIT and the Component
Model. It does not reuse the native FFI trampoline or expose linear memory:

```rpl
target(lang: ffi)

attrs (
    "rpl:wasm"
)

@wasm(
    wit: "example:users@1.0.0",
    world: "user-plugin",
    interface: "user-service",
    guest: "rust",
    hosts: "rust,go,js",
)
model UserService {
    Id uint64
    Name string
    Tags []string

func GetUser (id uint64) return (UserService?, error)
    func List return ([]UserService, error)
}
```

The output contains `world.wit`, a normalized IR snapshot, a deny-by-default
plugin manifest, a Rust `wit-bindgen` guest crate, a typed Rust Wasmtime host,
and generated host packages for Go and JS. A final RPL `error` return lowers
to WIT `result<T, string>`; traps remain runtime errors. Go guest generation is
still intentionally disabled.

See the [`WASM attr guide`](src/attrs/rpl:wasm/README.md),
[`WASM examples`](examples/11-wasm/README.md), and the
[`FFI/WASM architecture decision`](docs/ffi-and-wasm-plugins.md).

### `rpl:parser`

Parser turns one RPL model into a lexer, a PEG recursive-descent parser, and a
compact AST arena. Model fields declare tokens; methods declare grammar rules:

```rpl
attrs ("rpl:parser")

@parser(root: "Expr", goPackage: "exprparser")
model ExpressionGrammar {
    Space string @parser(pattern: "[ \\t\\r\\n]+", skip: true)
    Integer string @parser(pattern: "[0-9]+")
    Plus string @parser(literal: "+")

func Expr return () @parser(rule: "Integer (Plus Integer)*")
}
```

The rule language supports sequences, ordered alternatives (`|`), groups,
optional expressions (`?`), and repetition (`*`, `+`). Lexer selection uses
the longest match and optional numeric priorities. Regex patterns use Go RE2.

Generated `Arena.Nodes` and `Arena.Edges` are flat slices. `NodeID` and
`EdgeID` are `uint32` indexes, and allocation-free child traversal uses
`tree.Children(id)`. Nodes retain source spans and token ranges rather than
copying text. The analyzer rejects unknown symbols, invalid/empty regex tokens,
left recursion, and nullable repetitions before emitting code.

See the complete [`parser attr guide`](src/attrs/rpl:parser/README.md),
[`parser examples`](examples/13-parser/README.md), and the compilable
[`parser-arena project`](examples/projects/parser-arena/README.md).

### `rpl:json`

JSON adds standard-library struct tags directly to the primary generated Go
model. Put it on a model to tag every field, or only on selected fields:

```rpl
attrs ("rpl:json")

@json(case: snake, omitempty: true)
model APIResponse {
    RequestID string
    DisplayName string @json(name: "display", omitempty: false)
    RetryAfter int @json("retry_after,string")
    Secret string @json(ignore: true)
}
```

The short field form contains the exact value inside `json:"..."`. Named
arguments support `name`, `case`, `omitempty`, `omitzero`, `string`, and
`ignore`. Model defaults can be overridden with explicit `false`. Supported
naming modes are `camel` (default), `snake`, `kebab`, and `field`. Invalid tag
options and conflicting configurations are reported by both the CLI and VS
Code diagnostics.

See the [`JSON attr guide`](src/attrs/rpl:json/README.md) and the executable
[`JSON examples`](examples/14-json/README.md).

## CLI reference

Run `rpl help` for the installed version.

### Project commands

```text
rpl init [dir]
rpl new [dir]
```

Creates a project scaffold. Existing files are preserved.

### Generation

```text
rpl run <file.rpl>
rpl run <file.rpl> out <directory>
rpl generate <file.rpl> out <directory>
rpl gen <file.rpl> out <directory>
rpl g <file.rpl> out <directory>
```

Without `out`, the generator uses its normal schema-relative output behavior.
With `out`, the destination is resolved explicitly.

### Formatting

```text
rpl fmt <file.rpl>
rpl format <file.rpl>
```

Formats the schema in place using the compiler formatter. Field attr layout is
kept intentionally flexible: inline attrs remain inline, while `{ ... }` attr
blocks remain blocks. Use the form that is clearer for each field.

### Automatic imports and attrs

```text
rpl auto set import <file.rpl>
```

Analyzes used external Go types and attr namespaces and inserts missing
`import (...)` and `attrs (...)` declarations.

### Documentation

```text
rpl docs [file.rpl]
rpl doc [file.rpl]
```

Generates README documentation from a schema. If no path is supplied, RPL
looks for `src/main.rpl` and then `main.rpl`.

### Attr management

```text
rpl attr list
rpl attr info author:name
rpl attr init author:name
rpl attr init --global author:name
```

- `list` prints discovered manifests and versions;
- `info` prints one attr manifest;
- `init` creates an SDK v2 attr scaffold with analysis, generation,
  documentation, manifest, and README files;
- `init --global` creates the scaffold in the user-wide attrs directory.

The scaffold includes its own `go.mod` with a local `replace rpl => ...`
pointing at the SDK shipped beside the active RPL executable. On first discovery
RPL builds the missing attr binary automatically. Source-tree development can
override SDK lookup with `RPL_SDK_PATH=/path/to/rpl/src`.

### Configuration management

```text
rpl config show [--global]
rpl config path [--global]
rpl config init [--global]
```

Without `--global`, config commands operate on the current project. With it,
they operate on the user-wide RPL config and attrs directory.

### Runtime

```text
rpl runtime
```

Starts the JSON API over stdin/stdout for editors and other tools.

## Project configuration

RPL searches upward from the active schema for `.rpl/config.xml`. Project
settings are overlaid on the user-wide config. If neither file exists,
in-memory defaults are used.

```xml
<?xml version="1.0" encoding="UTF-8"?>
<config>
  <runtimes>
    <directory>.rpl/attrs</directory>
  </runtimes>
  <localization>
    <language>en</language>
    <color>true</color>
  </localization>
  <author_data>
    <author_name>Example Team</author_name>
  </author_data>
</config>
```

| Setting | Meaning |
| --- | --- |
| `runtimes/directory` | project-local attr directory |
| `localization/language` | diagnostic language (`en` or `ru`) |
| `localization/color` | ANSI output for CLI diagnostics |
| `author_data/author_name` | author inserted into generated metadata where supported |

### Global configuration and attrs

Create or inspect the per-user configuration with:

```text
rpl config init --global
rpl config path --global
rpl config show --global
```

The default location follows the operating system user config directory:

| Platform | Typical global config |
| --- | --- |
| Linux | `~/.config/rpl/config.xml` |
| macOS | `~/Library/Application Support/rpl/config.xml` |
| Windows | `%AppData%\rpl\config.xml` |

Set `RPL_CONFIG_HOME` when a portable toolchain, CI job, or editor sandbox needs
an explicit location. The global config uses the same XML shape as the project
config; relative runtime paths resolve from the global config directory.

Create one attr that is visible to every project:

```text
rpl attr init --global acme:audit
rpl attr list
rpl attr info acme:audit
```

Attr discovery has deterministic precedence:

1. the nearest project's configured attrs;
2. attrs configured in the global user config;
3. built-in attrs bundled next to the RPL executable.

The first matching `author:name` wins. A repository can therefore pin or
develop a project-local attr without deleting the globally installed version.
Global attrs make shared company generators and personal tooling available
without copying them into every repository.

### Config CLI

```text
rpl config show                 # effective config for the current project
rpl config path                 # nearest project config path
rpl config init                 # create .rpl/config.xml
rpl config show --global        # user-wide values only
rpl config path --global        # user-wide config path
rpl config init --global        # create user-wide config and attrs location
```

Project-local settings win for the active schema. Global localization is used
when a project does not override it. Attr directories are searched as separate
layers rather than merged into one writable folder.

## Runtime API and attr SDK

### JSON runtime actions

The stdin/stdout runtime exposes these actions:

| Action | Purpose |
| --- | --- |
| `run` | parse and compile code into an AST response |
| `check` | return compiler diagnostics without writing output |
| `format` | return formatted schema code |
| `auto.set.import` | return code with missing imports and attrs inserted |
| `lang` | set the active diagnostic language |
| `lang.current` | read the active diagnostic language |
| `attrs.get` | inspect one configured attr |
| `attrs.search` | list/search discovered attrs and their specs |
| `types.catalog` | return target types and structural snippets |

The VS Code extension keeps one runtime process alive and sends current
document text to these actions. Runtime failures are surfaced as diagnostics
instead of being hidden only in logs.

### Attr SDK

The SDK under [`src/pkg/sdk`](src/pkg/sdk) defines:

- attr manifests, capabilities, and versioned requests;
- schema/model/type snapshots;
- `AttrSpec` and typed attr arguments;
- analysis diagnostics and storage/file claims;
- model/file generation requests and responses;
- docs requests;
- Go file formatting and code-builder helpers;
- catalog, schema, declarations, runtime, and target convenience packages.

Start a local attr with:

```bash
rpl attr init acme:audit
```

The generated executable communicates with the compiler over stdin/stdout. An
attr advertises whether it can analyze/generate/docs at model or file scope,
and the compiler invokes only supported capabilities.

## VS Code extension

Download `rpl-language-support-0.6.1.vsix` from the release and run:

```text
Extensions: Install from VSIX...
```

The extension requires the RPL CLI in `PATH`, or an explicit binary selected
with `RPL: Select CLI Binary`.

### Editing features

- TextMate and semantic highlighting for `.rpl`;
- completion for keywords, models, target types, structures, attrs, and attr
  arguments discovered from the active runtime;
- hover documentation sourced from `AttrSpec`;
- persistent workspace compiler diagnostics, including closed `.rpl` files and
  Explorer file/folder problem decorations;
- quick fixes for missing attrs and Go imports;
- document formatting and optional format-on-save;
- automatic import/attr insertion on save;
- Outline and `Go to Symbol` for package, target, models, and fields;
- CodeLens actions above models: Generate, Check, Docs.

### Workspace UX

- an RPL Explorer view listing schemas, attrs, and toolchain state;
- editor-title Generate and Check actions;
- status bar and Language Status integration;
- a central RPL action menu;
- generated VS Code Tasks for Generate, Docs, and Format;
- output-channel logs and runtime restart controls;
- remembered generation output directory per schema.

### Extension settings

| Setting | Default | Purpose |
| --- | ---: | --- |
| `rpl.binaryPath` | `rpl` | CLI binary path |
| `rpl.enableDiagnostics` | `true` | live compiler diagnostics |
| `rpl.enableCompletions` | `true` | completion provider |
| `rpl.autoSetImportsOnSave` | `true` | update attrs/imports on save |
| `rpl.formatOnSave` | `true` | format through RPL runtime on save |
| `rpl.enableCodeLens` | `true` | model actions in the editor |
| `rpl.showStatusBar` | `true` | runtime and diagnostic state |
| `rpl.enableTaskProvider` | `true` | automatic workspace tasks |

Extension source and additional documentation live in
[`editors/vscode/rpl`](editors/vscode/rpl).

## Examples

[`examples`](examples) is a working cookbook:

| Directory | Topic |
| --- | --- |
| `00-syntax` | models, defaults, imports, model methods, field methods |
| `01-std` | comments, multi-group DTO projections, selective ignore rules |
| `02-validate` | scalar/list/optional rules, email, phone, URL, past time, hashes |
| `03-sql` | PostgreSQL/SQLite, composite keys, JSON fields, defaults, stores |
| `04-redis` | explicit/composite/fallback keys, TTL, complete hash codecs |
| `05-grpc` | nested messages plus classic, model/ID-bound, inside, ignored methods |
| `06-multifile` | one package split across RPL files |
| `07-imports` | importing another RPL schema |
| `08-mongodb` | ObjectID/BSON conversion, sparse indexes, search/sort, CRUD/watch |
| `09-transport` | six adapters, multi-routing, subjects, method-only services |
| `10-ffi` | C ABI, C/Rust servers, Go/Python/C/Rust clients |
| `11-wasm` | WIT, Rust Component guest, typed Wasmtime host, sandbox manifest |
| `12-enums` | uint-backed enums, typed variant data, imported Go structs/types |
| `13-parser` | PEG token/rule schemas, generated lexer, flat array/index AST arena |
| `14-json` | model-wide and field-level Go JSON struct tags |
| `99-showcase` | end-to-end combinations of built-in attrs |
| `projects` | standalone Go modules with app code, commands, and tests |

Run an example from the repository root:

```bash
go -C src run ./cmd run ../examples/03-sql/01-user-storage.rpl out /tmp/rpl-sql
go -C src run ./cmd run ../examples/05-grpc/01-basic-service.rpl out /tmp/rpl-grpc
go -C src run ./cmd run ../examples/99-showcase/main.rpl out /tmp/rpl-showcase
```

For realistic application structure, start with the
[`examples/projects`](examples/projects) collection:

| Project | Generated boundary | Handwritten boundary |
| --- | --- | --- |
| `account-service` | SQL store, SQLite schema, validation, metadata | validation-first account service and executor test double |
| `session-cache` | Redis key/hash codec, ignored fields, validation | cache entry boundary and round-trip tests |
| `process-service` | os.bin, HTTP, Unix, NATS, Kafka, WebSocket adapters | concurrency-safe user service and protocol tests |
| `grpc-service` | protobuf, gRPC client/server adapters, validation | in-memory domain service and TCP server |
| `ffi-service` | C ABI, Rust server trait, four client languages | generated Go client seam and native ABI contract |
| `enum-go-interop` | enum SQL columns/lists and imported Go domain types | domain methods, enum labels, typed payload tests |
| `parser-arena` | longest-match lexer, PEG parser, `NodeID`/`EdgeID` arena | indexed AST traversal and positional error tests |

Each project contains its own `.rpl/config.xml`, `go.mod`, `cmd/`, `internal/`,
README, and tests. Generated files are excluded so CI proves they can always be
recreated from the schema.

The focused plugin and language cookbook folders contain executable schemas. Every folder has
a feature-matrix README, and the compiler test suite regenerates every schema
in isolation so examples cannot silently become stale.

## Repository architecture

```text
.
├── Makefile
├── README.md
├── editors/
│   └── vscode/rpl/              VS Code extension
├── examples/                    executable schema cookbook
├── src/                         Go module
│   ├── attrs/                   bundled attr source modules
│   │   ├── rpl:std/
│   │   ├── rpl:validate/
│   │   ├── rpl:sql/
│   │   ├── rpl:mongodb/
│   │   ├── rpl:redis/
│   │   ├── rpl:grpc/
│   │   ├── rpl:transport/
│   │   ├── rpl:ffi/
│   │   ├── rpl:wasm/
│   │   ├── rpl:parser/
│   │   └── rpl:json/
│   ├── cmd/                     CLI entrypoint
│   ├── internal/
│   │   ├── cli/                 command implementations
│   │   ├── config/              XML config discovery and defaults
│   │   ├── formatter/           RPL source formatter
│   │   ├── generator/           parser, AST, analyzer, targets, runtime
│   │   ├── jsonapi/             editor/runtime request handlers
│   │   ├── plugins/             attr discovery, processes, scaffolding
│   │   └── service/             compiler/language/type services
│   └── pkg/
│       ├── error/               structured localized diagnostics
│       └── sdk/                 public attr SDK
└── test/app/                    generated-code integration fixture
```

### Generation lifecycle

1. Locate project configuration relative to the requested schema.
2. Load the file and related package/import files.
3. Parse source into the AST and resolve types, groups, methods, and defaults.
4. Discover declared attrs and query their capabilities/specs.
5. Run compiler and attr analysis; merge structured diagnostics.
6. Plan base target and attr-generated files and reject conflicting claims.
7. Format generated Go source and write the output atomically.
8. Update `.rpl-generated.json` and remove obsolete generated sidecars.

## Development and testing

### Common commands

```bash
make help
make test
make test-attrs
make test-projects
make build-host
make build-all
make release
make plugin
make clean
```

### Go tests

```bash
go -C src test ./...
go -C src vet ./...
```

`make test` runs the core package suite and then every built-in attr. Attr tests
are invoked from their directories because runtime directory names contain
`author:name` identifiers.

`make test-projects` performs the strongest example check: it copies every full
project without generated files, builds its attrs, regenerates the module,
asserts key generated APIs, and runs that module's `go test ./...`. These tests
are also part of the compiler package selected by `make test`.

### Integration fixture

```bash
cd test/app
go test ./...
```

See [`test/README.md`](test/README.md) for the boundary between unit tests,
built-in attr tests, the legacy fixture, and full generated-project tests.

The fixture compiles generated models, validation, SQL, protobuf, gRPC client,
and gRPC server packages together.

For consumer code examples across every bundled attr, see the
[`generated plugin API cookbook`](docs/generated-plugin-api.md).

### VS Code tests and package

```bash
cd editors/vscode/rpl
npm test
vsce package
```

### Building all release targets

```bash
make build-all
```

Default matrix:

- `darwin/arm64`, `darwin/amd64`;
- `linux/arm64`, `linux/amd64`;
- `windows/arm64`, `windows/amd64`.

Each target contains the portable CLI, compiled sidecar attrs, and attr SDK.

## Release builds

Create the complete release bundle with:

```bash
make release
```

This builds the six OS/architecture targets, bundles every attr and the SDK,
packages the VS Code extension, creates `.tar.gz`/`.zip` archives, and writes
`checksums.txt` under `build/release/v<version>/`. All RPL binaries are portable
across machines.

Release assets include SHA-256 checksums. Verify them before installing:

```bash
shasum -a 256 -c checksums.txt
```

## Troubleshooting

### `attr ... was not found`

Run:

```bash
rpl attr list
```

Confirm that `.rpl/attrs` is still beside the installed executable or that the
project's `.rpl/config.xml` points to a valid local attr directory.

### Runtime or VS Code diagnostics are unavailable

Check:

```bash
rpl help
rpl runtime
```

In VS Code, use `RPL: Show Toolchain Status`, inspect the RPL Output channel,
and set `rpl.binaryPath` if the CLI is not on `PATH`.

### An external Go type cannot be resolved

Declare its Go import in the schema or run:

```bash
rpl auto set import path/to/schema.rpl
```

For gRPC inside-method inspection, the imported Go package must be available to
the active Go toolchain/module cache.

### Generated protobuf files are missing

Confirm that the schema declares `rpl:grpc`, applies `@grpc()`, and that the
protobuf tools required by the development environment are installed. Inspect
the compiler diagnostic detail; subprocess output is preserved.

### Output contains stale files

Generate through RPL rather than copying individual generated files. RPL uses
`.rpl-generated.json` to track ownership and remove obsolete sidecars safely.

### ANSI output or diagnostic language is wrong

Update `.rpl/config.xml`:

```xml
<localization>
  <language>en</language>
  <color>false</color>
</localization>
```

## License

RPL is released under the [Apache License 2.0](LICENSE).

rpl

오너의 다른 레포

파일 탐색기

# CDN으로 사용하기

# 프로젝트 배지

Was this content helpful?

Recent Feedback

rpl

오너의 다른 레포

파일 탐색기

# CDN으로 사용하기

# 프로젝트 배지

Was this content helpful?

Recent Feedback

Download README