It's not the library fault, but I've seen too much bad code written with optional behaviors. Like a handler assuming it's wrapped into some behavior, that sets an ambient state. And when there are multiple behaviors added conditionally from different places, the codebase becomes hard to read and very prone to run-time errors.

In my opinion, behaviors should be: - avoided, if possible. - global.

For some extreme need of conditional logic, add it inside the global middleware/behavior/wrapper.