- See previously BP Dev Chat summary (July 10)
- In attendance: @espellcaste @boonebgorges @tw2113 & @im4th
- Slack archive
Feedbacks about 4.4.0 Security & Maintenance release
4.4.0 has been released on July 23rd and has been downloaded more than 30,000 times since then. No specific feedbacks were posted on our support forums about it. We’ll keep an eye on how it evolves in the coming days but it looks like it went smoothly.
BP REST API
@espellcaste shared his worries about the time remaining until 5.0.0 release. I think it’s still doable and if we’re short, we will be able to use our « test drive » as a fallback. We’ll only have to buy a domain name more meaningful.
As discussed during the previous dev-chat, I’ve started writing the documentation into the « WordPress Handbook » format copy-pasting parts of the Restsplain generated documentation. Here’s a first page for the Components endpoint.
The interesting benefit about doing so is the fact it’s a good way to review the BP REST API. If members of the team want to participate to this effort, they just need to ping @im4th to get admin access to the site.
To illustrate the benefit described in the above paragraph, I’ve (I am @im4th 😁) shared this pull request (#196) about improving the consistency of the Component’s endpoint
PUT method arguments description/documentation. @espellcaste will look into it and check the other endpoints about the subject.
@espellcaste also worked on adding hooks to the
prepare_links() methods when needed and to items collection query parameters. He will also look into this issue to try to understand why a notice error is thrown when removing the avatar original file.
Finally, although @dcavins couldn’t attend our dev-chat, he’s been hardly working on adapting the BP REST API (197) to go along with the new Invitation API (#6210) he’s been building for BuddyPress. I will look into it more deeply asap. My very first feedback would be to rebase the pull request as there is one merge conflict (probably due to the hooks recently added by @espellcaste)
5.0.0 milestone’s tickets
At the end of the previous topic, @im4th informed he would probably open a new ticket to improve the
bp.apiRequest : the
dataType argument should default to
json, doing so it will save some time to plugin developers using it in the future as REST replies are in JSON.
We did a quick review of the “new” tickets having patches, in particular @boonebgorges and @im4th talked about #8013 to decide about the name of the additional key to use for the exporter item names displayed to regular users. @im4th agreed with @boonebgorges it was best to
bp prefix the name.
About the list of patches I mentioned into the July 10th’s dev-chat summary. I’ve decided to commit the three crossed out ones (the first 3, if you prefer) below and leave some more time to the BP Legacy Twenty Nineteen companion stylesheet.
#8013: BuddyPress Data Export Screen should not show WordPress/BuddyPress to users #8026: Default avatar choices show same generated icon in general discussion settings #8079: BP Site-wide Notices: To enable paragraphs in the body text of the notification.
- #8103 : BP-Legacy needs a companion stylesheet for Twenty Nineteen
About this last ticket, it would be great to have some feedbacks about it as I’m unsure I made the right
CSS decisions about it.
BuddyPress & the Gutenberg project
As requested by @espellcaste into this comment of the dev-chat agenda we kept some time to discuss about this topic or more precisely about the first ideas we have to benefit from the Gutenberg project (Phase 1 – editor & Phase 2 – widgets).
The first very important thing @im4th wanted to highlight is:
BuddyPress Blocks will be easier to create by us or plugin developers thanks to the BP REST API: I think it’s a very important point, because the Gutenberg project mainly use REST.
I’ve been thinking about this since the dev-chat and I think we really need to have this ticket fixed for 5.0.0 release : #8116 BP Blocks category.
Then we had difficulties to understand each others and I think that’s because the Block Editor is often called Gutenberg 😇.
Theme Compat API “vs” Block API
@boonebgorges shared very important points comparing the Block API to our Theme compatibility API.
Gutenberg does something similar to what our theme compat does. It provides a way to place dynamic content in the “content” area of a theme template.
Retrospectively, I would add that the Gutenberg team is working on a “JSON templating” feature, but I’m unsure it will be overridable : I think “overridability” is a great feature of our Theme Compat API.
What does the BuddyPress community want/need ?
@espellcaste think it’s important we get our community members expectations about this topic.
another thing I think would be important is to see what the community want… try to get the info somehow…. specially from bp theme authors…
A lot of things could be improved but that doesn’t mean it will have the most impact…
I think he’s 100% right, so instead of dropping the ideas we talked about during the dev-chat, I guess we need to organize them a little and let you give us your opinions about it. It would help us a lot to decide what will be our next steps into this area. So stay tuned! We’ll soon be back to you 🤗.