The Wayback Machine - https://web.archive.org/web/20220323121232/https://github.com/topics/events
Skip to content
#

events

Here are 2,977 public repositories matching this topic...

watermill
xorcare
xorcare commented Nov 22, 2021

This comment says that the message ID is optional,
but for SQL transport it is a mandatory attribute,
in turn it causes misunderstanding?

Is it possible to fix it or did I get something wrong?

https://github.com/ThreeDotsLabs/watermill/blob/b9928e750ba673cf93d442db88efc04706f67388/message/message.go#L20
https://github.com/ThreeDotsLabs/watermill/blob/b9928e750ba673cf93d442db88efc04706f6

help wanted good first issue S
evankanderson
evankanderson commented Dec 3, 2021

Problem

Sugar Controller is a separate install, which makes its functionality less useful.

Similar to knative/serving#11969, remove sugar-controller as a separate installable YAML, and integrate it into the main eventing controller. Use a namespace-level label selector to enable and disable the sugar controller at the namespace level.

The [current documenta

kind/feature-request help wanted area/eventing good first issue
hennevogel
hennevogel commented Feb 23, 2022

There are currently the following views

  • app/views/proposal/new.html.haml with a form to create a new Event
  • app/views/proposal/form.html.haml with the edit view
  • app/views/proposal/edit.html.haml with 3 lines of html of the edit view
  • app/views/proposal/_proposal_form.html.haml with form to edit an Event

This should be cleaned up into new, edit view and a form parti

good first issue refactoring 🔧

Improve this page

Add a description, image, and links to the events topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the events topic, visit your repo's landing page and select "manage topics."

Learn more