Proposal

Now when you're quite comfortable with the codebase we have, let's try a bit different approach. Instead of doing step-by-step instruction, let's try the way how developers do it. I mean, let's try a format where there is a description including pieces of information rather than exact steps.

Description

We need to make our GH Commit Block be able to fetch data from our REST API.

To achieve that we will use a field for saving a commit hash there.

When a commit hash is pasted to the text field, we need to fetch data from REST API to save commit-related data to the block's attributes.

Let's see how GB works with client-rendered blocks. We need to replace our render callback with a save function in JS instead.

Caveat, you will fetch data in the edit and create an HTML markup in save according to attributes (updated during "edit"), so we just save the resultant block to the DB.

As a result we would look like the following:

What might be useful

• How to use a control toolbar
• How to fetch data from API