v0.2.0

Features

• Interpretation Context — New context parameter (zasis_tt_interpret_context) on the interpreter interface, allowing key-value pairs to be passed to custom logic and event producers (#12, #14)
• HTTP Context Support — POST requests accept an optional context array in the JSON body, forwarded to the interpreter (#14)
• Input Validation — Interpreter raises an error when string_to_be_interpreted is empty/missing, returning HTTP 400 with a clear message
• Instance-based Custom Logic Resolver — Refactored custom logic instantiation to a resolver pattern (zasis_if_customlogic_resolver), improving testability and separation of concerns (#19)

Bug Fixes

• REPLACE no-match handling — REPLACE rules with non-matching regex now correctly return 'no match' instead of the original string (#23)
• Uncaught exception lint errors — Added proper exception handling to resolve abaplint uncaught exception findings (#20)

Tests & Documentation

• Expanded unit test coverage with edge cases and integration scenarios (#22)
• Added 5 new HTTP integration tests (context, empty input, wrong content-type, unsupported method) — 12 total
• Updated README for accurate service setup and current package structure (#11)

Issues Closed

• #12 — Add interpretation context passing
• #14 — HTTP handler: Accept and forward interpretation context from POST body

Breaking Changes

• POST requests with an empty or missing string_to_be_interpreted now return HTTP 400 instead of 200 with empty results
• zasis_if_interpreter~execute now has an additional optional parameter context