idea: consider a shared type-conversion primitive if a second config format needs one #38

Open
opened 2026-07-19 20:32:15 +02:00 by michael · 0 comments
Owner

Summary

config_parser.lua's convert() currently recognizes exactly two types
beyond plain strings: numbers (strict decimal format, see
DAW/daw-lua-common team review 2026-07) and booleans (true/false).

Noted during the 2.0.0 team review as a "keep in the back of your
mind, not now" idea: if config values with units or other typed
formats are ever wanted (e.g. timeout = 30s, size = 64M, uuid or
decimal values), convert() could eventually grow into a small,
separate internal conversion primitive shared across parsers, rather
than each parser reinventing its own ad-hoc type recognition.

Explicitly not a task right now

No current requirement drives this. Building it now would be
overengineering for a need that doesn't exist yet. This issue exists
purely so the idea isn't lost, in case a second parser (or a config
value type request) makes it relevant later.

Refs

DAW/daw-lua-common (2.0.0 team review, config_parser.lua discussion)

## Summary config_parser.lua's convert() currently recognizes exactly two types beyond plain strings: numbers (strict decimal format, see DAW/daw-lua-common team review 2026-07) and booleans (true/false). Noted during the 2.0.0 team review as a "keep in the back of your mind, not now" idea: if config values with units or other typed formats are ever wanted (e.g. `timeout = 30s`, `size = 64M`, uuid or decimal values), convert() could eventually grow into a small, separate internal conversion primitive shared across parsers, rather than each parser reinventing its own ad-hoc type recognition. ## Explicitly not a task right now No current requirement drives this. Building it now would be overengineering for a need that doesn't exist yet. This issue exists purely so the idea isn't lost, in case a second parser (or a config value type request) makes it relevant later. ## Refs DAW/daw-lua-common (2.0.0 team review, config_parser.lua discussion)
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
DAW/daw-lua-common#38
No description provided.