Bug: Graphql not inline with Font Awesome search

Bug description

The data that comes back from the graphql API is not inline with how the filters work on Font Awesome.

When filtering on Font Awesome, there are 3 families and 6 styles.

Families:

• Classic
• Sharp
• Brands

Styles:

• Solid
• Regular
• Light
• Thin
• Duotone

But the data that comes back from the graphql is the following:

  "data": {
    "search": [
      {
        "familyStylesByLicense": {
          "pro": [
            {
              "family": "sharp",
              "style": "solid"
            },
            {
              "family": "sharp",
              "style": "regular"
            },
            {
              "family": "sharp",
              "style": "light"
            },
            {
              "family": "duotone",
              "style": "solid"
            },
            {
              "family": "classic",
              "style": "thin"
            },
            {
              "family": "classic",
              "style": "solid"
            },
            {
              "family": "classic",
              "style": "regular"
            },
            {
              "family": "classic",
              "style": "light"
            }
          ]
        },
        "id": "coffee-pot"
      }
    ]
  }
}

What you can see here is that duotone has become a family instead of a style. This makes it really inconsistent to work with if you want to make an icon picker for example. Filtering out the right icons is harder now even as displaying it in a font-awesme component.

Would be nice if duotone would become a style in the graphql as well. Family should be classic. Duotone doesn't even exist for sharp.

In addition, maybe it is a good idea to also add the array based syntax to the FamilyStyle. This way we get back the actual value of the combined styles, because a sharp light icon has the following value: fasl.

Thanks in advance!

Reproducible test case

No response

Screenshots

No response

Font Awesome version

v6.4.0

Serving

Self-hosted

Implementation

SVG+JS, Other (as specified in the bug description)

Browser and Operating System

NA

Web bug report checklist

• I have included a test case because my odds go way up that the team can fix this when I do
• I have searched for existing issues and to the best of my knowledge this is not a duplicate