FPL Strict Mode: Check Your Custom Processors

The FPLv2 engine now follows JavaScript strict-mode rules. An assignment to a variable that was never declared, such as a = 1, now fails validation. Processors from the Fluency repository are already updated. Processors written or edited on your own instance should be checked.

What to check

Open each processor you created or edited yourself on the Processors page and choose Validate. If validation fails on an undeclared variable, declare it where it is first assigned:

let a = 1

What else changed

Boolean expressions now short-circuit: if a && a.b { ... } returns false when a is null or undefined, where the old engine raised an error. Guards like this, common in JavaScript, now work as written.

Details are in the FPL Engine Update: Strict Mode release notes.

Splash Summary

The FPLv2 engine now follows JavaScript strict-mode rules. An assignment to a variable that was never declared, such as a = 1, now fails validation. Processors from the Fluency repository are already updated. Processors written or edited on your own instance should be checked.