Name field uniqueness scope sits at the Custom Component level?

[daniel-rogers-gh]

Not sure if this is a bug or feature request. If I attempt to add an entry with the same Name to multiple custom components I receive the error:

You must enter a unique Custom Component name and short name!

What I want to do is this:

[
  {
    "Id": 1,
    "ParentComponent": "environmentshortname",
    "Name": "Development",
    "ShortName": "dev",
    "SortOrder": 1,
    "MinLength": "2",
    "MaxLength": "3"
  },
  {
    "Id": 2,
    "ParentComponent": "environmentpropername",
    "Name": "Development",
    "ShortName": "Development",
    "SortOrder": 2,
    "MinLength": "2",
    "MaxLength": "20"
  }
]

I know this might fly in the face of convention, but our team settled on Subscriptions having Proper Case (environmentpropername) purpose/environment names. All resources below this level would only use the abbreviated short code names (environmentshortname).

To that end I wanted to add multiple components that could be attributed to the correct resources, whether they use the proper or abbreviated versions.

The only other thing I can think of is to alter the name fields to something like:

• Development - Abbreviated
• Development - Proper Case

Could the Name uniqueness scope be shifted down to the Custom Component level or is facilitating this fundamentally flying in the face of this tool's purpose?

Edit: It seems spaces can't be present in the short name fields, so this wouldn't allow us to achieve what we want anyway (e.g. Non Production won't be valid). I might exclude subscriptions from the tool for now.