Conceptslatest · 0.1.2
package.hws rules
package.hws is checked before anything is built. Every problem is listed in one run, with line and column for JSON errors.
JSON
- Strictly valid JSON: no comments and no trailing commas. A UTF-8 byte-order mark is accepted.
- No duplicate keys, including keys that differ only in case (
Versionandversion). Workspace reads names case-insensitively, so either could silently win.
Fields
| Field | Rule |
|---|---|
Name | Required. |
Code | Required. Upper-case letters, digits and underscores, starting with a letter. A Horizech code must match its type: HWS_CORE, HWS_APP_…, HWS_PLUGIN_…, HWS_PROVIDER_…, HWS_THEME_…. |
Version | Required. A semantic version, e.g. 1.4.0 or 2.0.0-beta.1. |
Info.Type | Required (except for HWS_CORE). Core, App, Plugin, Provider or Theme. |
AssemblyName | Required except for themes. The backend's .dll file name; it must be in the build output. |
MainFile | Required except for themes. |
Frontend.RemoteEntry | Required when there is a Frontend section. A plain path inside dist/; the file must exist after the build. |
Frontend.RemoteUrlOverride | Not allowed. It is a local development setting that points an instance at a developer's machine. |
Strings may not have leading or trailing spaces.
Types in the registry
| Info.Type | Registry type |
|---|---|
| Core | CORE (creating one needs a Horizech root account) |
| App | APPLICATION |
| Plugin | PLUGIN |
| Provider | PROVIDER |
| Theme | none: packable, not publishable |