We use decision template is based on ''using patterns to capture architectural decisions'' and arc42 decisions
Decisions need to:
- be implementable within the next major release
- be according to Elektra's goals
To add a new decision copy template.md and add a link in the appropriate
section here.
- Unit Testing
- Script Testing
- Bootstrap
- Empty Files
- CMake Plugins
- Logging
- Elektra Web Structure
- Elektra Web Recursive Structure
- Cryptographic Key Handling
- Relative Storages
- Deferred Plugin Calls
- High-level API
- High-level API Help Message
- Global KeySet
- Rest API Documentation
- Commit Function
- Error codes
- Error Message Format
- Error code implementation
- Default Values
- Semantics for Name
- Base Name
- Lookup every key
- Holes and Non-leaf values
- Multiple File Backends
- Ensure (@kodebach)
- Null
- Memory Layout
- Iterators
- Simplify API (@lawli3t will make proposal of new API)
- Binary
- Store the escaped and/or unescaped key name
- Remove functions copying into buffer