Skip to content

Releases: MagPasulke/abap-string-interpreter

v0.5.0

30 May 20:18
f7b32d8

Choose a tag to compare

0.5.0 (2026-05-30)

Features

  • add adt_gitpull custom tool for OpenCode (#58) (d66cc31)
  • add adt_rununit OpenCode tool for remote ABAP unit test execution (#62) (a5e0b15)
  • deploy-sap workflow — auto abapGit pull after CI passes on main (#59) (7f42251)
  • enhance adt_gitpull to support pulling from different branches (#65) (5b1fc4c)

Bug Fixes

  • ci: add --esm flag to tsx to support top-level await in CI runner (#60) (5e0b1ed)
  • ci: replace top-level await with async IIFE in CI runner (#61) (b8995c5)
  • ci: split typecheck into ci and local variants (ca1a5f1)
  • structured JSON error responses for HTTP API (cab73f2)

v0.4.0

28 May 20:57
9ed13b1

Choose a tag to compare

What's Changed

⚠ Breaking Changes

  • interpreter: migrate regex from POSIX to PCRE (#53) — regex patterns must now use PCRE syntax instead of POSIX

Features

  • interpreter: include interpretation context in interpreter result (#54)
  • interpreter: add ABAP Doc comments to all public methods and interfaces (#45)
  • lint: add performance abaplint rules (#34)
  • add naming & hygiene abaplint rules (#39)
  • add version interface and pre-commit version sync hook (#25)

Bug Fixes

  • align DDIC structure naming to _line suffix convention (#50)
  • resolve potential bugs - RETURN in loop, overly broad CATCH (#42)
  • inline variable declarations to resolve abaplint prefer_inline errors (#38)
  • technical debt - typos, dead code, inconsistent casing (#40)
  • utils: check sy-subrc after SELECT and READ TABLE in domain fix values query provider (#35)
  • migrate http-test env from VS Code settings to http-client.env.json (#52)

v0.2.0

21 May 08:41
3528e37

Choose a tag to compare

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

v0.0.1

18 May 21:25
3bdfaab

Choose a tag to compare

Initial release