decisions

Introduction

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.

Implemented

• Unit Testing
• Script Testing
• Library Split
• 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
• Ingroup Removal
• Commit Function
• Error Message Format
• Default Values
• High Level API
• Error codes
• Error code implementation

Decided

• Array for Warnings

In Discussion

• Semantics for Name
• Base Name
• Store the escaped and/or unescaped key name
• Sources for Metadata
• Lookup every key
• Holes and Non-leaf values
• Arbitrary Meta-Data
• Multiple File Backends
• Capabilities
• Array
• Boolean
• Global Plugins
• Vendor Spec
• Plugin Variants
• Global Validation

Rejected

• CMake spec
• Null Pointer Checks
• Elektra Web Publish Subscribe
• Internal Cache