Set up Verbaly in a project
verbaly_initCreates the config file and locale catalogs, detects the bundler or meta-framework, and names the package to add and line to wire. Keeps existing files, so re-running is safe.
Instructions
Create the config file and the locale catalogs, and detect the bundler or meta-framework so the answer names the package to add and the line to wire (what verbaly init does). A file already there is kept, never overwritten, so running it again is safe. Use it when verbaly_doctor finds no config; once the project is set up, verbaly_doctor is the one to run.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "verbaly_init"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| dir | No | Directory for the catalogs (default: locales) | |
| root | No | Project root holding verbaly.config (defaults to the server working directory) | |
| locales | No | Every locale, source included | |
| sourceLocale | No | The language you write in (default: en) |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| host | No | Bundler or meta-framework detected from the dependencies | |
| next | Yes | What a human still has to do, in order | |
| found | No | Catalogs the project already had, which the new config points at | |
| created | Yes | Files written, relative to the project root | |
| refused | Yes | Locales left out: not a locale tag, and no sure way to fix one | |
| renamed | Yes | Locales written with the hyphen a locale tag takes (pt_BR became pt-BR) | |
| skipped | Yes | Files already there, left untouched | |
| configFile | Yes |