As a Developer who is getting started with OpenPF2, I'd like it if the assertion checks in BlueprintCallable code were softer, so that if a blueprint becomes out-of-date or unintentionally passes-in a nullptr for a required parameter, I get an error message instead of Unreal Engine crashing.
Acceptance Criteria
Given I'm calling a BlueprintCallable function from a blueprint and I pass a null value into a required parameter:
I'd expect either that the blueprint would not compile or that I'd get an error in the logs.
I'd expect Unreal Engine not to crash.
I'd expect the call to have no other side effects (i.e. it should return early upon detecting the missing parameter value).
As a Developer who is getting started with OpenPF2, I'd like it if the assertion checks in
BlueprintCallablecode were softer, so that if a blueprint becomes out-of-date or unintentionally passes-in anullptrfor a required parameter, I get an error message instead of Unreal Engine crashing.Acceptance Criteria
Given I'm calling a
BlueprintCallablefunction from a blueprint and I pass anullvalue into a required parameter: