Sort DNS Records such that multiple records with same name are grouped

[humphd]

In #438 we are moving to allow DNS Records of type A, AAAA, and TXT (i.e., not CNAME) to have multiple values. Our current UI assumes this is always a single value. We need to make 2 changes:

1. DNS Records table needs to be able to show one or more values. We could join them with , for example
2. The New DNS Record and Edit DNS Record form needs to allow for one or more input boxes for the value(s). You should be able to add or remove input boxes to include multiple values. By default we'd show only 1.

[Myrfion]

1. Only one CNAME record per one fqdn, validation has to enforce it
2. For all other types A, AAA, TXT we allow multiple records each with a different value

[cychu42]

1. Only one CNAME record per one fqdn, validation has to enforce it
2. For all other types A, AAA, TXT we allow multiple records each with a different value

@Myrfion Let me know if I understand this correctly:
For A, AAA, TXT type, I can create two DNS records with same name and type, as long as values are different.
For CNAME type, I should only have one DNS record.

[Myrfion]

@cychu42 sorry just seen your message on this one, the issue got resolved in your PR right?

[humphd]

When a user has more than 1 record with the same name and different type, it would be nice to "group" them together by sorting the results:

[humphd]

NOTE: @dadolhay suggests adding the value + name together as the sort key. You can talk to him for more info.

[ghost]

const recordsSorted = records.sort(
  (({subdomain: aSubdomain, type: aType}, {subdomain: bSubdomain, type: btype}) =>
    [...aSubdomain].reverse().join('').localeCompare([...bSubdomain].reverse().join('')) ||
    atype.localeCompare(btype)
  );

• reverse both subdomains
• compare them
• If equal, then compare the record type the same way

This is not tested, you might need to change the compare order (like compare b with a instead of a with b)

[cychu42]

@cychu42 sorry just seen your message on this one, the issue got resolved in your PR right?

I only added restriction to not duplicate CNAME records, and restriction on other record type duplication is currently in place.