What's new in Customer Journeys?

Connect and learn more!
Resolving issues in auto-generated Javascript files found by Sonarqube — Cloud Customer Connect
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Resolving issues in auto-generated Javascript files found by Sonarqube

Accepted answer
edited Nov 29, 2023 4:31PM in Visual Builder 2 comments


Can these issues found by Sonarqube in Javascript code auto-generated by Visual Builder be resolved without consequences for Visual Builder / our webapp?

Content (please ensure you mask any confidential information):

Recently, we’ve started analyzing code quality using Sonarqube as our static code analysis tool. Some of our projects are web apps, developed with Oracle Visual Builder.

We downloaded our current project files from Git (Visual Builder Studio) to have sonar-scanner analyze the code on our local machine (laptop) and send the results to Sonarqube. As soon as we enabled to also scan the project’s .js files, the analysis showed a large number of ‘code smells’ in the .js files, most of which were auto-generated by Visual Builder.

Howdy, Stranger!

Log In

To view full details, sign in.


Don't have an account? Click here to get started!