Contributing

Pull requests are welcome — bug fixes, new helpers and documentation improvements alike.

Reporting Issues

Please open an issue at the main repository. When reporting a bug, include:

• ABAP release and language version (Standard / Cloud / 7.02)
• The shortest reproducible snippet
• Expected vs. actual behavior
• Stack trace from lx->get_text( ) if relevant

Development Setup

1. Fork the abap-util/abap-util repo.
2. Clone it into an SAP system via abapGit (see Installation).
3. Install the npm tooling locally if you want to run the offline unit tests:

   npm install

4. Useful scripts:

   npm run downport        # rewrite sources for the 702 branch
   npm run auto_transpile  # transpile ABAP to JS via abaplint
   npm run unit            # run unit tests in node

Coding Guidelines

• Add helpers to zabaputil_cl_util whenever they fit the existing prefix groups (c_, rtti_, time_, …).
• Cover every new helper with an ABAP Unit test in the corresponding *.testclasses.abap file.
• Avoid release-specific syntax in the façade. If a helper needs a cloud-only or on-prem-only API, put the implementation into zabaputil_cl_util_api_c / _api_s and call it through zabaputil_cl_util_api.
• Run abaplint locally before committing — the CI will reject lint failures.

Pull Requests

• Keep PRs focused: one feature or one fix per PR.
• Reference the issue you fix (e.g. Fixes #123).
• Update or add documentation in the docs repo when the public API changes.

Code of Conduct

The project follows the contributor Code of Conduct. By participating you agree to abide by it.

License

abap-util is released under the MIT License. Contributions are accepted under the same license.