Conduct prop audit as a team

This issue is to conduct a prop audit as a team and determine next steps for prop conventions or renames for the next major release.

Topics to discuss:

• Conventions for className
• Conventions for ref
• Conventions for event handler signatures
• Convention for open vs isOpen
• Convention for render* props
• Convention for aria-label vs label
• Convention for size variants
  • Do we use a size prop, or is the size itself a prop?

Related issues:

• https://github.com/carbon-design-system/carbon/issues/5853

[joshblack]

@metonym thanks for the input! Love these ideas.

Only one note, for the shortening prop name step I believe we’ll move forward with isFixed instead of fixed. The rationale being that lowercase prop names can be confused with DOM attributes in some cases. There is also confusion as to if states named similarly to something like active correspond to the initial state or the current state. This is something which is* can help to address as a naming convention 👍

We can definitely do this on a case-by-case basis, but might make more sense just to have one convention across the codebase so the API becomes more guess-able instead of being component-specific.

[joshblack]

Going to close this in favor specific audit lists 👀