Recent blocks shows empty at times

[mtias]

@notnownikki haven't debugged this one, but I've seen the recent blocks inserter ending up empty in different occasions.

[notnownikki]

That's super weird, never seen that happen! When you saw it then, were you changing tab back to recent, or just clicking on the inserter?

[mtias]

Just clicking on the inserter.

[notnownikki]

What browser are you using? I can't reproduce this one 😞

I can see in the screenshot that you've got blocks added, so this suggests one of the following:

1. Adding a block to the recently used list is going wrong, and we end up with an empty list - I can't see how this would happen, but lines 229-248 in editor/state.js are where this happens so if we see it happening, that's where we need some debug to find out if it's happening there.

2. Connecting the redux state to the component is not getting the correct state. This is the part of the react/redux lifecycle I understand the least, so it's possible that's messing up somehow, but right now I can't see how.

I don't think this is anything to do with the search state, because the tabs are still rendering, so we're not searching - if we were, there would be no tabs.

[westonruter]

@notnownikki I can reproduce this by opening an existing post in Gutenberg. Even though I have blocks in my content already, since I haven't actually inserted any blocks since I loaded the page, there is no data yet to populate the recent blocks. Is this not the same as #1859?

[notnownikki]

Oh! Ok, it's not the same, as it seems I haven't hooked into all the correct actions, and #1859 is about providing the API for the current code to use. Thanks, I'll get on this, it should just be a matter on taking down which actions need to be responded to.

[notnownikki]

Should be fixed in #1920

[hedgefield]

Have the same issue after updating to 0.5.0. It happens every time I open an existing post in gutenberg, like weston said.

[notnownikki]

@hedgefield thanks for verifying 😄 I have a branch where this is fixed, we're just making sure that everything is in the right place and named correctly, as it introduces some hooks for loading and saving user specific data (such as block usage!)

[aduth]

Should be fixed by #1920