[ckan-changes] [okfn/ckan] fa3bfc: [#3028] Add `followee_list` and `followee_count` a...

[GitHub]

  Branch: refs/heads/3028-dashboard-activity-stream-filtering
  Home:   https://github.com/okfn/ckan
  Commit: fa3bfc719e9eacf5d2534f5a57becc8b68093b65
      https://github.com/okfn/ckan/commit/fa3bfc719e9eacf5d2534f5a57becc8b68093b65
  Author: Sean Hammond <seanhammond at lavabit.com>
  Date:   2012-12-10 (Mon, 10 Dec 2012)

  Changed paths:
    M ckan/logic/action/get.py
    M ckan/tests/functional/api/test_follow.py

  Log Message:
  -----------
  [#3028] Add `followee_list` and `followee_count` action functions


  Commit: b75d0463b0d1cb8c4aa39f497b484357d9f1a3e3
      https://github.com/okfn/ckan/commit/b75d0463b0d1cb8c4aa39f497b484357d9f1a3e3
  Author: Sean Hammond <seanhammond at lavabit.com>
  Date:   2012-12-10 (Mon, 10 Dec 2012)

  Changed paths:
    M ckan/logic/action/get.py

  Log Message:
  -----------
  [#3028] Add search filtering to followee_list


  Commit: 965640c41712b60e637196f856eb0d603b778ab4
      https://github.com/okfn/ckan/commit/965640c41712b60e637196f856eb0d603b778ab4
  Author: Sean Hammond <seanhammond at lavabit.com>
  Date:   2012-12-10 (Mon, 10 Dec 2012)

  Changed paths:
    M ckan/logic/action/get.py
    M ckan/tests/functional/api/test_follow.py

  Log Message:
  -----------
  [#3028] Change format of dicts returned by followee_list

Match the format requested by @johnmartin for the frontend


  Commit: c9039b65b8dc4b90b775c67bf9160fbc8cc115f8
      https://github.com/okfn/ckan/commit/c9039b65b8dc4b90b775c67bf9160fbc8cc115f8
  Author: Sean Hammond <seanhammond at lavabit.com>
  Date:   2012-12-10 (Mon, 10 Dec 2012)

  Changed paths:
    M ckan/model/activity.py

  Log Message:
  -----------
  [#3028] Refactor a couple of activity streams methods

Refactor _activites_from_users_followed_by_user_query() and
_activites_from_datsets_followed_by_user_query(), make them use an
SQLAlchemy union of _user_activity_query() for all users followed by the
given user and _package_activity_query() for all datasets followed by
the given user, respectively.

This just ensures that what appears in a user's public activity stream,
for example, is exactly what will appear in your dashboard activity
stream if you follow that user. Better than having two different
implementations of the SQL for this query.

_activites_from_groups_followed_by_user_query() already works this way.


Compare: https://github.com/okfn/ckan/compare/fa3bfc719e9e^...c9039b65b8dc