Up until now, the override_flag test util was only useful to completely activate or deactivate a flag. It didn't allow to provide more customization for all the internal checks it makes, like evaluating if the request user is authenticated or staff.
This change provides that functionality, without breaking the current API, to avoid breaking changes. Now, users can provide more granular arguments to override_flag, for a more flexible flag testing.
clintonb
commented
1 year ago
Up until now, the
override_flagtest util was only useful to completely activate or deactivate a flag. It didn't allow to provide more customization for all the internal checks it makes, like evaluating if the request user is authenticated or staff.This change provides that functionality, without breaking the current API, to avoid breaking changes. Now, users can provide more granular arguments to
override_flag, for a more flexible flag testing.Closes #439.