eventsvc

type EventCreatedRequest ¶

type EventCreatedRequest struct {
	Id int `json:"id"`
}

type EventCreatedResponse ¶

type EventCreatedResponse struct {
	Err error `json:"-"`
}

func (r *EventCreatedResponse) Body() interface{}

func (r *EventCreatedResponse) Failed() error

type EventPublisher ¶

type EventPublisher struct {
	// contains filtered or unexported fields
}

EventPublisher implements Service on the publisher side.

EventPublisher should only be used in limited scenarios where only one subscriber is involved and the publisher depends on the interface provided by the subscriber.

In typical use cases of the publish-subscribe pattern - many subscribers are involved and the publisher knows nothing about the subscribers - you should just send the event in the way it should be.

func NewEventPublisher(publisher eventpubsub.Publisher, codecs eventcodec.Codecs) *EventPublisher

func (p *EventPublisher) EventCreated(ctx context.Context, id int) (err error)

type Service ¶

type Service interface {
	//kun:event type=created
	EventCreated(ctx context.Context, id int) error
}

Service is used for handling events.

type Subscriber ¶

type Subscriber struct{}

func (s *Subscriber) EventCreated(ctx context.Context, id int) error