Conversation
PR SummaryLow Risk Overview When the script-runner microservice is enabled, the Blade view now exposes Reviewed by Cursor Bugbot for commit e5a2002. Bugbot is set up for automated code reviews on this repo. Configure here. |
|
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Want higher recall? High effort reviews run extra passes and find more bugs. A team admin can switch effort levels in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit e5a2002. Configure here.
| <script> | ||
| if (!!{{ config('script-runner-microservice.enabled') }}) { | ||
| window.Processmaker.script_microservice = { | ||
| enabled : {{ config('script-runner-microservice.enabled', false) }}, |
There was a problem hiding this comment.
Disabled microservice breaks inline script
Medium Severity
Blade prints a boolean false as an empty string, so script-runner-microservice.enabled being off yields invalid JavaScript (if (!!) and enabled : ,). That parse error aborts the whole inline script, including the packages setup that follows. The original layout avoided this with a Blade @if so the block was omitted when the microservice is disabled.
Reviewed by Cursor Bugbot for commit e5a2002. Configure here.







Issue & Reproduction Steps
Describe the issue this ticket solves and describe how to reproduce the issue (please attach any fixtures used to reproduce the issue).
Solution
How to Test
Describe how to test that this solution works.
Related Tickets & Packages
Code Review Checklist