HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
sadlil
go-trigger
Go2016–2016
sadlil / go-trigger

go-trigger

A Global event triggerer for golang. Defines functions as event with id string. Trigger the event anywhere from your project.

2Distinct people
7Mentions
0Explicit recommenders
250GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A Global event triggerer for golang. Defines functions as event with id string. Trigger the event anywhere from your project.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by day7 dated mentions

Observed mentions: 2016-02-24 15:54:23 UTC to 2016-03-16 16:29:35 UTC.

0122016-02-24 00:00:00 UTC to 2016-02-25 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsFeb 242016-02-25 00:00:00 UTC to 2016-02-26 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2016-02-26 00:00:00 UTC to 2016-02-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-02-27 00:00:00 UTC to 2016-02-28 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-02-28 00:00:00 UTC to 2016-02-29 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-02-29 00:00:00 UTC to 2016-03-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2016-03-01 00:00:00 UTC to 2016-03-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-03-02 00:00:00 UTC to 2016-03-03 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2016-03-03 00:00:00 UTC to 2016-03-04 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2016-03-04 00:00:00 UTC to 2016-03-05 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-03-05 00:00:00 UTC to 2016-03-06 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsMar 52016-03-06 00:00:00 UTC to 2016-03-07 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-03-07 00:00:00 UTC to 2016-03-08 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-03-08 00:00:00 UTC to 2016-03-09 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-03-09 00:00:00 UTC to 2016-03-10 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-03-10 00:00:00 UTC to 2016-03-11 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-03-11 00:00:00 UTC to 2016-03-12 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-03-12 00:00:00 UTC to 2016-03-13 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-03-13 00:00:00 UTC to 2016-03-14 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-03-14 00:00:00 UTC to 2016-03-15 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-03-15 00:00:00 UTC to 2016-03-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-03-16 00:00:00 UTC to 2016-03-17 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsMar 16

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Feb 242016-02-24 00:00:00 UTC2016-02-25 00:00:00 UTC110
Feb 252016-02-25 00:00:00 UTC2016-02-26 00:00:00 UTC110
Feb 262016-02-26 00:00:00 UTC2016-02-27 00:00:00 UTC000
Feb 272016-02-27 00:00:00 UTC2016-02-28 00:00:00 UTC000
Feb 282016-02-28 00:00:00 UTC2016-02-29 00:00:00 UTC000
Feb 292016-02-29 00:00:00 UTC2016-03-01 00:00:00 UTC211
Mar 12016-03-01 00:00:00 UTC2016-03-02 00:00:00 UTC000
Mar 22016-03-02 00:00:00 UTC2016-03-03 00:00:00 UTC110
Mar 32016-03-03 00:00:00 UTC2016-03-04 00:00:00 UTC110
Mar 42016-03-04 00:00:00 UTC2016-03-05 00:00:00 UTC000
Mar 52016-03-05 00:00:00 UTC2016-03-06 00:00:00 UTC000
Mar 62016-03-06 00:00:00 UTC2016-03-07 00:00:00 UTC000
Mar 72016-03-07 00:00:00 UTC2016-03-08 00:00:00 UTC000
Mar 82016-03-08 00:00:00 UTC2016-03-09 00:00:00 UTC000
Mar 92016-03-09 00:00:00 UTC2016-03-10 00:00:00 UTC000
Mar 102016-03-10 00:00:00 UTC2016-03-11 00:00:00 UTC000
Mar 112016-03-11 00:00:00 UTC2016-03-12 00:00:00 UTC000
Mar 122016-03-12 00:00:00 UTC2016-03-13 00:00:00 UTC000
Mar 132016-03-13 00:00:00 UTC2016-03-14 00:00:00 UTC000
Mar 142016-03-14 00:00:00 UTC2016-03-15 00:00:00 UTC000
Mar 152016-03-15 00:00:00 UTC2016-03-16 00:00:00 UTC000
Mar 162016-03-16 00:00:00 UTC2016-03-17 00:00:00 UTC110

What Hacker News says

7 sources
Neat idea, thanks for posting this! I readily admit I'm absolutely guilty of implementing this sort pattern repeatedly across many go apps, and haven't ever [yet] gotten to making a generic implementation :) Some interesting notes (with a few curiosities): * This reminds me a lot of how jinzhu implemented the gorm [0] callbacks system. * The triggering is all global rather than per-instance (you can't create a new "trigger" struct). I wonder why this pattern was selected rather than allowing more fine-grained control and groups via instances. * Looking at the open PRs, #1 [1] was a surprise: Adding multiple listeners to one event enhancement Does go-trigger really not support multiple subscribers to an event? I wonder why it wasn't architected that way from the start. [0] https://github.com/jinzhu/gorm [1] https://github.com/sadlil
Read the rest
In Go-trigger

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.