[DAEMON-105] config: Able to set a sub-key for keys that should not allow subkeys
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | High |
| Status | Resolved |
| Resolution | Fixed |
| Resolution Date | 2017-10-26T22:46:09.000+0000 |
| Affected Version/s | Appc Daemon 1.0.0 |
| Fix Version/s | Appc Daemon 1.0.0 |
| Components | appcd-core |
| Labels | n/a |
| Reporter | Ewan Harris |
| Assignee | Chris Barber |
| Created | 2017-10-24T13:02:20.000+0000 |
| Updated | 2017-10-26T22:46:09.000+0000 |
Description
Description
Calling something like the below will set a key on the property even though the key is a boolean in the JSDoc, this occurs on master and my appcd config PR branch
appc config set telemetry.enabled.bar x
ws.send(JSON.stringify({
version: '1.0',
path: '/appcd/config',
id: Date.now(),
data: {
"action": "set",
"key": "telemetry.enabled.bar",
"value": "x"
}
}));
No comments