You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi Team, thanks a lot for all the efforts to create and update the styleguides.
By now we got rid of most of our own ABAP rules and replaced them with the styleguide. Is there any chance to also have this for SAPUI5 and maybe even CAP development? 🙏
Strictly speaking, these are the "SAP Code Style Guides" and therefore are not limited by name to ABAP.
I know there are some general rules on the respective sites of the frameworks, but they are by far not as well maintained and currated as this guide.
Therefore an respetive extension would be much appreciated!
The text was updated successfully, but these errors were encountered:
SAP did publish a Clean SAPUI5 style guide, but unfortunately only as a book. As we all know, books are the most fitting medium for the ever-changing nature of web development. 😉
Snarky comments aside, I really hope that SAP eventually publishes their Clean SAPUI5 style guide as an open-source guideline as well. The Clean ABAP style guide has set a great precedent on the benefits of this approach.
It was the original intention when we started the style guide repository for ABAP to do the same for other languages / frameworks. So far we could not find motivated colleagues who can continuously commit sufficient amount of time to create and maintain such a guide for SAPUI5 or CAP in an Open Source manner.
Hi Team, thanks a lot for all the efforts to create and update the styleguides.
By now we got rid of most of our own ABAP rules and replaced them with the styleguide.
Is there any chance to also have this for SAPUI5 and maybe even CAP development? 🙏
Strictly speaking, these are the "SAP Code Style Guides" and therefore are not limited by name to ABAP.
I know there are some general rules on the respective sites of the frameworks, but they are by far not as well maintained and currated as this guide.
Therefore an respetive extension would be much appreciated!
The text was updated successfully, but these errors were encountered: