Add Known Limitations section to README #10
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
residual/config#10
Loading…
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?
Problem
The README documents features well but doesn't list known limitations. External users should know what the library doesn't support before investing time.
Known Limitations to Document
Conf tags with double quotes —
conf:"foo\"bar"produces malformed struct tags. Conf tags must not contain double quotes. (Documented in code comment atcore/tag.go:183, not in README.)Non-string map keys —
map[int]stringis not supported. Onlymap[string]Tworks.MergeWithRules wildcard matching — Wildcard patterns (
database.*) match against the leaf field name, not the full dotted path. This is a known limitation documented incore/merge.go:50-53.Non-string slice env vars — Before #8 is fixed: env var overlays only support
[]stringslices. Other types ([]int,[]bool) are silently skipped. After #8 is fixed, this item should be removed from the list.No
map[string]Tsupport — Before #7 is fixed. After #7 is fixed, remove this item.Fix
Add a "Known Limitations" section to README.md after "Supported Formats":
Files
README.md