Provide context to the `bp_is_user_spammer` filter

[dd32]

The bp_is_user_spammer() functions filter bp_is_user_spammer filter only passes the result of the function through it, but doesn't pass the actual $user or $user_ID of which the filter is acting upon.

[dd32]

See ​https://github.com/buddypress/buddypress/pull/11

[imath]

Hi @dd32

Thanks a lot for your suggestion, we’ll add it in next minor version. Too bad our Trac doesn’t have the same feature the WordPress one has to support PRs on GitHub 😉.

[dd32]

Too bad our Trac doesn’t have the same feature the WordPress one has to support PRs on GitHub 😉.

When someone adds me to the ​BuddyPress organisation as an owner so I can set it up, ​I shall ;)

[imath]

Awesome thanks a lot @dd32 I’m asking it to JJJ 👍

Trac Ticket: ​https://buddypress.trac.wordpress.org/ticket/8645

[imath]

In 13254:

Add a GitHub template for pull requests

Pull Requests made on the BuddyPress GitHub repository are only used for code reviews and must be linked to a BuddyPress trac ticket. This template explains this fact and provides the contributor some guides.

Props dd32

See #8645

[imath]

In 13255:

Provide context to bp_is_user_spammer & bp_is_user_deleted filters

These two filters now include a second parameter to pass the WP_User object.

Props dd32

See #8645 (trunk)

[imath]

In 13256:

Provide context to bp_is_user_spammer & bp_is_user_deleted filters

These two filters now include a second parameter to pass the WP_User object.

Props dd32

Fixes #8645 (branch 10.0)

[imath]

In 13258:

Edit the GitHub pull requests template

Fix a missing "WordPress/BuddyPress" replacement about the inline comment informing where to paste the BuddyPress trac ticket link.

See #8645