I believe labels (for blocks) should default to their content type, if the user-provided angular expression results in a null or whitespace.

[markadrake]

The default behavior of a block is to use its
content type as the label.

The following screenshots show the default configuration of any block you would add, and the resulting label value in a block list.

Is there any reason why somebody would
desire a blank label?

Now, let's set a custom label to our block. We'll use something that we know results in null or empty, and see what the editor's experience is like.

If the angular expression results in null or whitespace
I propose we default the label back to its content type.

In a recent project, I had to go back through (approaching ~40) various block settings and append || $contentType to the end of each angular expression. While this approach worked for most of my blocks, it doesn't work when the values return whitespace, such as the example below.

{{ copy | ncRichText | truncate:true:35 || $contentType }}

If my proposal is not clear,

• Reduce the amount of data entry I need to do by defaulting all block labels to $contentType, as you already do today.
• Expand this to cover two conditions. If the angular expression used for the label results in:
  1. null
  2. whitespace

Then, the above example could be simplified to just:

{{ copy | ncRichText | truncate:true:35 }}

...and work.