The specs define separately provider EVENTS and provider STATUS. This PR doesn't quite yet introduce ProviderStatus, but rather extends the Events to include all the possible statuses (namely adding notReady). I am not sure if this compromise can be acceptable in the long run, or if we'll need to eventually add the Statuses separately. Nevertheless adding notReady gives the Providers a proper case to use at initialization time.
Related Issues
~Shall we add the lack of ProviderStatus as an Issue?~
(There is a proposal to remove ProviderStatus from Provider)
The specs define separately provider EVENTS and provider STATUS. This PR doesn't quite yet introduce
ProviderStatus, but rather extends the Events to include all the possible statuses (namely addingnotReady). I am not sure if this compromise can be acceptable in the long run, or if we'll need to eventually add the Statuses separately. Nevertheless addingnotReadygives the Providers a proper case to use at initialization time.Related Issues
~Shall we add the lack of
ProviderStatusas an Issue?~ (There is a proposal to remove ProviderStatus from Provider)