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
• 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

Mostly Implemented

• Array for Warnings
• Array
• Boolean
• Reference Counting

Decided

• Capabilities
• Make elektraMalloc et al. private
• Elektra Prefix

In Progress

• Iterators
• Simplify API (@lawli3t will make proposal of new API)
• Binary
• Store the escaped and/or unescaped key name
• Remove functions copying into buffer

In Discussion

• keyString() return value
• Global Plugins (@mpranj)
• Error Semantics (API)
• Error Handling
• Spec Expressiveness
• Metadata in Spec Namespace
• Library Split

Drafts

• Notifications
• Library Directory Structure
• Header File Structure

Delayed

• Plugin Variants
• Global Validation

Rejected

• Key Name as separate class
• CMake spec
• Null Pointer Checks
• Elektra Web Publish Subscribe
• Internal Cache
• Vendor Spec