forked from Silverfish/proton-bridge
4ee6da4baa
Rather than having the services subscribe to each individual event type, have only one subscriber for the whole event object. This spreads the logic to the service through the `EventHandler` type. This is important for the next stage where the IMAP service will be required to apply events from the past.
35 lines
1.1 KiB
Go
35 lines
1.1 KiB
Go
// Copyright (c) 2023 Proton AG
|
|
//
|
|
// This file is part of Proton Mail Bridge.
|
|
//
|
|
// Proton Mail Bridge is free software: you can redistribute it and/or modify
|
|
// it under the terms of the GNU General Public License as published by
|
|
// the Free Software Foundation, either version 3 of the License, or
|
|
// (at your option) any later version.
|
|
//
|
|
// Proton Mail Bridge is distributed in the hope that it will be useful,
|
|
// but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
// MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
// GNU General Public License for more details.
|
|
//
|
|
// You should have received a copy of the GNU General Public License
|
|
// along with Proton Mail Bridge. If not, see <https://www.gnu.org/licenses/>.
|
|
|
|
package userevents
|
|
|
|
// Subscribable represents a type that allows the registration of event subscribers.
|
|
type Subscribable interface {
|
|
Subscribe(subscription EventSubscriber)
|
|
Unsubscribe(subscription EventSubscriber)
|
|
}
|
|
|
|
type NoOpSubscribable struct{}
|
|
|
|
func (n NoOpSubscribable) Subscribe(_ EventSubscriber) {
|
|
// Does nothing
|
|
}
|
|
|
|
func (n NoOpSubscribable) Unsubscribe(_ EventSubscriber) {
|
|
// Does nothing
|
|
}
|