Our tests previously was written in a way what created a blank authenticator object, and then configured it one config at the time. I want to transition away from that, as it makes traitlets verification of config error if any of the incremental configuration steps after the authenticator object is initialized are invalid - even though the final configuration won't be.
By this change, we align better with how users are going to use their authentication class which is typically initialized by jupyterhub itself based on config provided, rather than initialized without provided config and then updated.
Our tests previously was written in a way what created a blank authenticator object, and then configured it one config at the time. I want to transition away from that, as it makes traitlets verification of config error if any of the incremental configuration steps after the authenticator object is initialized are invalid - even though the final configuration won't be.
By this change, we align better with how users are going to use their authentication class which is typically initialized by jupyterhub itself based on config provided, rather than initialized without provided config and then updated.