In specific cases - i.e. when using Drupal in a headless system -, setting a target may be required as not doing so might result in invalid HTML (like an empty target attribute) if the consuming frontend doesn't check values.
Thus, making the selection of a target required on the CMS is a solution to force the editor to make a choice.
N/A
Add an option to specify what attributes must be required.
Create MR
Review MR
Merge MR
Extra option to make an attribute required.
None.
An attribute can be set required.
Active
2.0
Code
I've added the option to set attributes required. But for some reason the empty option is still there. Can't really find out if this module is responsible for that or it's something else.
This will need work to provide test coverage for the required options.