idea: consider a shared type-conversion primitive if a second config format needs one #38
Labels
No labels
coordination/cross-repo
coordination/needed
effort
large
effort
medium
effort
small
meta/duplicate
meta/planning
meta/wontfix
priority
high
priority
low
priority
medium
session
blocker
session
handover
session
next
status
blocked
status
done
status
in-progress
status
review
status
to-go
type
admin
type
bug
type
config
type
deployment
type
docs
type
enhancement
type
feature
type
handover
type
infrastructure
type
installation
type
maintenance
type
migration
type
research
type
security
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
DAW/daw-lua-common#38
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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 ordecimal 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)