Blacklist API sucks
Bug #612344 reported by
Michal Hruby
This bug affects 5 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Unity |
Invalid
|
Undecided
|
Unassigned | ||
Zeitgeist Framework |
Fix Released
|
Medium
|
Manish Sinha (मनीष सिन्हा) | ||
unity-lens-files |
Invalid
|
Low
|
Unassigned | ||
unity-place-files (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Guys, GetBlacklist and SetBlacklist (without any signals) for an asynchrounous-
How about changing it to Get, Add, Remove and a changed signal? That way it'd be actually usable...
Related branches
lp:~manishsinha/zeitgeist/new-blacklist-implementation
- Markus Korn: Approve
- Mikkel Kamstrup Erlandsen: Approve
-
Diff: 251 lines (+103/-43)2 files modified_zeitgeist/engine/extensions/blacklist.py (+86/-27)
test/blacklist-test.py (+17/-16)
Changed in zeitgeist: | |
assignee: | nobody → Michal Hruby (mhr3) |
Changed in zeitgeist: | |
importance: | Undecided → Medium |
status: | New → Triaged |
assignee: | Michal Hruby (mhr3) → Seif Lotfy (seif) |
Changed in zeitgeist: | |
milestone: | none → 0.6 |
Changed in unity: | |
status: | New → Triaged |
importance: | Undecided → Low |
Changed in unity-place-files: | |
importance: | Undecided → Low |
status: | New → Triaged |
Changed in zeitgeist: | |
milestone: | 0.7.0 → none |
Changed in zeitgeist: | |
milestone: | none → 0.7.0 |
affects: | unity → null |
Changed in zeitgeist: | |
status: | Triaged → In Progress |
Changed in zeitgeist: | |
milestone: | 0.7.0 → 0.8.0 |
Changed in unity: | |
status: | New → Triaged |
Changed in unity-place-files (Ubuntu): | |
status: | New → Triaged |
Changed in unity-place-files: | |
status: | Triaged → Invalid |
Changed in unity: | |
status: | Triaged → Invalid |
Changed in unity-place-files (Ubuntu): | |
status: | Triaged → Invalid |
Changed in zeitgeist: | |
status: | In Progress → Fix Committed |
Changed in null: | |
status: | Triaged → Invalid |
Changed in zeitgeist: | |
status: | Fix Committed → Fix Released |
no longer affects: | null |
To post a comment you must log in.
I suggest you post a full API draft before implementing this. We have the current (admittedly not-so-good) API because it was hard coming up with a nice API for this.