You can no longer use unregisterBlockType() with core blocks

[sheepzilla]

Issue Overview

After the update to 2.1.0 the sample code to unregister core blocks taken from the Gutenberg handbook no longer works as expected.
https://wordpress.org/gutenberg/handbook/extensibility/#using-a-whitelist

It looks like the initial registering of the blocks has been moved in the following commit:
e694f6a

Can the docs be updated to reflect this change?

Steps to Reproduce (for bugs)

1. Add whitelist code from https://wordpress.org/gutenberg/handbook/extensibility/#using-a-whitelist to a theme or plugin and load in the admin
2. Observe that while editing a page all blocks are still available.

Expected Behavior

Expected behaviour would be for only the specified blocks to be available.

Current Behavior

All blocks available

[taija]

Also seeing this issue. Any workarounds?

[gziolo]

I might break something with the recent refactoring. I will debug later this week and hopefully push a patch. Aplogies for temporary inconvenience :)

[gziolo]

This is the same issue as described and explained by @youknowriad in #4848. We started exploring different ways of registering blocks to come up with a much reliable solution. You can see what has been proposed already in #2751. Code explorations are done in #4841. So the idea would be to have full control over which blocks are going to be registered on PHP side.

I will close this one as a duplicate of #4848, but I would expect API change really soon so this is won't fix.