Lars Hvam

enabling https://rules.abaplint.org/uncaught_exception/ can help with the first type (if the rule is not too buggy)

Any thoughts on how to handle the reports, dynpros and gui frontend stuff? Perhaps split the code into backend and examples?

its not possible with a single codebase targeting 702 when it contains SELECTs, Steampunk applies strict SQL, strict SQL is not possible in 702(introduced in 7.40, SP05), having a automatic...

there are the following outside of demos, most of these can be refactored to avoid the SELECT, 

yea, so above is the import errors, not the activation errors. Activation should give more errors, like https://github.com/abap2xlsx/abap2xlsx/pull/926

yes, pull requests welcome 😄 https://blogs.sap.com/2022/01/03/steampunk-released-abap-api-first-draft-is-up/ is one tool to help the process, but its still lots of work, many issues to be tackled

class `cl_xml_document`

note that abap2xlsx aims for 702 compatibility, so inline declarations are not possible

1 issue from linter: is https://github.com/abap2xlsx/abap2xlsx/pull/1056 waiting to be merged

I've used Teams, with paid company account. In Slack its not possible to share stuff without paid account.