♻️ Use displayName from Classification model

[mnigh]

♻️ Refactor

Remove need to combine classification.level and classification.group when classification.displayName is all that is needed in some cases.

Example

🙋‍♀️ Proposed Solution

Add displayName accessor from Classification model to schema.graphql for use in queries for frontend. Add displayName to queries where needed.

type Classification {
  displayName: String! 
}

✅ Acceptance Criteria

• no uses of classification.level and classification.group when classification.displayName is what is needed
• no instances iterating over classifications with map to combine group and level

[petertgiles]

Depending on how you feel about ternaries...

Both languages have idiomatic ways of left padding strings:

[vd1992]

Depending on how you feel about ternaries...

Both languages have idiomatic ways of left padding strings

That does look cleaner for sure