From c57e52fc458a5bd39638f24782537ce275ab266e Mon Sep 17 00:00:00 2001 From: Attila Csanyi Date: Fri, 28 Apr 2017 22:50:40 +0200 Subject: [PATCH] doc: fix renamed uhk-config.json to user-config (#289) --- shared/src/config-serializer/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/shared/src/config-serializer/README.md b/shared/src/config-serializer/README.md index 9b7e62e0..14a521e2 100644 --- a/shared/src/config-serializer/README.md +++ b/shared/src/config-serializer/README.md @@ -12,7 +12,7 @@ Given that the development dependencies are installed on your system you should There are 3 different representations of the configuration, each filling a specific purpose. -The **JavaScript representation** is optimally suited to be serialized as JSON, and saved to the file system, or transmitted over the network. As a plaintext format, it's human-readable and easily editable. See [uhk-config.json](uhk-config.json) for an example configuration. +The **JavaScript representation** is optimally suited to be serialized as JSON, and saved to the file system, or transmitted over the network. As a plaintext format, it's human-readable and easily editable. See [user-config.json](user-config.json) for an example configuration. The **TypeScript representation** is structurally similar to the JavaScript representation, but it features strongly typed TypeScript objects instead of typeless JavaScript objects. This representation is meant to be used by Agent. Extensive, per-property [assertion](assert.ts) takes place upon initializing the TypeScript objects to ensure the integrity of the configuration.