[buddypress-trac] [BuddyPress Trac] #9200: BuddyPress core actions and filters as JSON

buddypress-trac noreply at wordpress.org
Mon Jun 24 01:58:36 UTC 2024


#9200: BuddyPress core actions and filters as JSON
------------------------------+--------------------------
 Reporter:  espellcaste       |       Owner:  espellcaste
     Type:  task              |      Status:  assigned
 Priority:  normal            |   Milestone:  Up Next
Component:  Build/Test Tools  |     Version:
 Severity:  normal            |  Resolution:
 Keywords:  needs-patch       |
------------------------------+--------------------------
Description changed by espellcaste:

Old description:

> The need to have this data came initially by me trying to create a vscode
> extension that used BuddyPress ''data'' (have autocomplete support for
> everything BP related).
>
> And I was inspired by this project [https://github.com/wp-hooks
> /wordpress-core-hooks https://github.com/wp-hooks/wordpress-core-hooks]
>
> But similarly to #9199, I learned afterwards that BuddyPress' hooks and
> actions have a lot of incorrect information. And several hooks were not
> properly generated due to the way they were added/created.
>
> I tried this at first [https://github.com/renatonascalves/bp-
> hooks/tree/main here] and [https://packagist.org/packages/renatonascalves
> /bp-hooks here].
>
> This ticket was created as a reminder, and for visiblity. The task of
> exporting the actionc and filters as JSON is pretty straightforward, so
> currently the only impediment is the correctness of the signatures of
> those actions and filters.
>
> A git repo, https://github.com/buddypress/bp-hooks, was created two years
> ago to hold this data. We should also make this available to
> [https://packagist.org packagist.org], when ready.

New description:

 The need to have this data came initially by me trying to create a vscode
 extension that used BuddyPress ''data'' (have autocomplete support for
 everything BP related).

 And I was inspired by this project [https://github.com/wp-hooks/wordpress-
 core-hooks https://github.com/wp-hooks/wordpress-core-hooks]

 But similarly to #9199, I learned afterwards that BuddyPress' hooks and
 actions have a lot of incorrect information. And several hooks were not
 properly generated due to the way they were added/created.

 I tried this at first [https://github.com/renatonascalves/bp-
 hooks/tree/main here] and [https://packagist.org/packages/renatonascalves
 /bp-hooks here].

 This ticket was created as a reminder, and for visibility. The task of
 exporting the actions and filters as JSON is pretty straightforward, so
 currently the only impediment is the correctness of the signatures of
 those actions and filters.

 A git repo, https://github.com/buddypress/bp-hooks, was created two years
 ago to hold this data. We should also make this available to
 [https://packagist.org packagist.org], when ready.

--

-- 
Ticket URL: <https://buddypress.trac.wordpress.org/ticket/9200#comment:1>
BuddyPress Trac <http://buddypress.org/>
BuddyPress Trac


More information about the buddypress-trac mailing list