Contribution
abap2UI5 is an open-source project built by the ABAP community, often in free time or alongside other projects. All kinds of contributions are welcome.
How You Can Contribute
There are several ways to get involved and help:
- Improve the framework itself — a fix, a frontend action, a test. A UI5 control or property needs no addition: the view builder writes any of them as it is, and the legacy builder with a method per control is frozen
- Build a custom control for your own specific scenario and share it
- Share your demos and apps to showcase what's possible with abap2UI5
- Improve the documentation and polish code snippets to make abap2UI5 easier to learn
- Propose something new — every contribution is appreciated, no matter the size
Turn Answers into Documentation
The cheapest contribution is one you have already half-made. When a question comes up on Slack or in an issue for the second time, make the answer permanent. There are three places for it:
- an entry in Common Failures, when the question starts from an error message
- a paragraph on the page that should have answered it
- a check that makes the mistake impossible to merge, when a script can decide it
The whole project works this way. Every defect found by hand becomes a rule, a reference example or a check, so nobody has to discover it twice. A written answer helps every future reader; a Slack thread helps one.
Need Help?
If you hit any issues or have questions, open an issue.