Add check for unsupported plugin name in plugin header field

[ernilambar]

Fixes #805

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: ernilambar <[email protected]>
Co-authored-by: davidperezgar <[email protected]>
Co-authored-by: swissspidy <[email protected]>
Co-authored-by: frantorres <[email protected]>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[ernilambar]

Tests are failing due to unrelated issue with this PR.

Edit: Tests are passing now.

[ernilambar]

@frantorres has suggested to modify the conditional and make less strict. Like:

Check if plugin name "has at least 5 latin letters (A-z), numbers, spaces, and hyphens" and not worry if there are other non valid characters around.

[davidperezgar]

I think that you meant @frantorres

[ernilambar]

I have updated the conditional to make less strict. Current message looks off after new conditional:

The "Plugin Name" header in the plugin file is not valid. It may only contain latin letters (A-z), numbers, spaces, and hyphens.

Can you please suggest updated message?

[frantorres]

Maybe

The "Plugin Name" header in the plugin file is not valid. It needs to contain at least 5 latin letters (a-Z) and/or numbers. This is necessary because the initial plugin slug is generated from the name.