)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":9816,"name":"Takashi Kajinami","email":"kajinamit@oss.nttdata.com","username":"kajinamit"},"change_message_id":"c7944e26963505626966f6370e532fc20b13e3b7","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"dc39e6d1_8948c330","updated":"2026-10-09 17:53:24.000000000","message":"After discussion in irc I totally agree with implementing the type validation. Honestly I thought it had been there, but in fact only default values were validated.\n\nHowever I think the current implementation has one problem. ConfigType itself doesn\u0027t contain full information about validation. For example you define a new config option with constraints such as `IntOpt(\u0027foo\u0027, min\u003d0, max\u003d10)` then you need to use that specific instance for validation . Using the class results in using `IotOpt()` which doesn\u0027t honor these min/max.\n\nI suspect we don\u0027t need these type register but really have to get a mapping of section/name: ConfigType *instance* to do validation.","commit_id":"f4820fa58e3558180074e6a3c09f2350184fcfe9"},{"author":{"_account_id":9816,"name":"Takashi Kajinami","email":"kajinamit@oss.nttdata.com","username":"kajinamit"},"change_message_id":"2160cbfc57b1390459d13cd95d8c40167e2509dc","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"e462c239_d2fb2838","in_reply_to":"dc39e6d1_8948c330","updated":"2026-10-09 17:54:10.000000000","message":"to be more clear\n\n\u003e Using the class results in using IotOpt() which doesn\u0027t honor these min/max.\n\nUsing the class *type* (not class instance) results in using IotOpt() which doesn\u0027t honor these min/max.","commit_id":"f4820fa58e3558180074e6a3c09f2350184fcfe9"}]}