Private schema property instead of underscore prefix in name

[TeamDijon]

Everything is in the title. I was pretty surprised to find the private blocks managed using a prefix in the file name instead of leveraging a property inside the schema, where it would be more logic in my opinion. I was wondering if said property was on the roadmap ?

It would look like that:

// blocks/block-name.liquid

{% schema %}
{
  "name": "Block name",
  "private": true,
  "...": "..."
}
{% endschema %}

Instead of:

// blocks/_block-name.liquid

{% schema %}
{
  "name": "Block name",
  "...": "..."
}
{% endschema %}

Of course, for backward compatibility, legacy underscore prefix shall remain, I'm just curious if this prefix convention may appear elsewhere in the future ?

[AlfalfaAnne]

This would be much preferred over the underscore prefix. Would make backwards compatibility with existing sites WAY easier. At the moment, it seems easier to make all of their blocks public to keep a clean upgrade path. Adding this property would allow us to keep the same JSON for templates because as long as the block names in blocks/**.liquid remain the same as they are defined in "type", everything works smoothly. But if we're forced to add a __ to those file names, then the JSON block references also have to be updated everywhere.

[TeamDijon]

Good point, I'm currently starting from scratch with theme blocks but I dread the day of a migration !