[buddypress-trac] [BuddyPress Trac] #8048: BuddyPress Blocks !

buddypress-trac noreply at wordpress.org
Sun Mar 15 22:09:56 UTC 2020


#8048: BuddyPress Blocks !
-------------------------+---------------------
 Reporter:  imath        |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  6.0.0
Component:  REST API     |     Version:
 Severity:  normal       |  Resolution:
 Keywords:  has-patch    |
-------------------------+---------------------
Changes (by imath):

 * keywords:  needs-patch => has-patch


Comment:

 8048.patch is containing:

 - the BP Blocks code to merge into Core
 - it replaces `grunt-wp-i18n`  by WP CLI i18n command (to ensure
 JavaScript translations)
 - it adds devDependencies for `parcel-bundler`, `@babel/core` and
 `@wordpress/babel-preset-default`
 - it adapts the build process for BP Blocks
 - it adds a `src/js` directory containing the development versions of the
 blocks.

 `npm start` is like a grunt watch for these Block JavaScript files
 `npm run build` is used to build the Block JavaScripts into 2 Grunt tasks.
 During the build process, the first one is done without minifying scripts
 to make sure Translations are generated by WP CLI, the second one is used
 after this translation step and minifies the scripts.

 Unlike what I thought in the first place, I believe it's best to merge the
 BP Blocks into Core completely (Thanks @johnjamesjacoby for making me
 thought about it twice !).

 I chose to add un-minified built Block JavaScript files into `/src` so
 that people starting to contribute to BuddyPress has no other steps to
 accomplish than checking out Trunk.

 About the PHP part, I've added a specific BP_Block class and some other
 specific functions.

 Feedbacks welcome ;)

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


More information about the buddypress-trac mailing list