As part of https://github.com/ni/nimble/pull/1078 : Enable TurboSnap for Chromatic tests - we exported DesignSystem.tagFor(ComponentClass) for each Nimble component.
We should use the new tag names consistently in Nimble instead of DesignSystem.tagFor where it makes sense (i.e. not for injecting the component registered to a base class but for when tags are used directly).
Looks like there are quite a few uses of DesignSystem.tagFor() in Nimble code and a couple references to it in CONTRIBUTING too: github search.
🧹 Tech Debt
As part of https://github.com/ni/nimble/pull/1078 : Enable TurboSnap for Chromatic tests - we exported DesignSystem.tagFor(ComponentClass) for each Nimble component.
We should use the new tag names consistently in Nimble instead of
DesignSystem.tagFor
where it makes sense (i.e. not for injecting the component registered to a base class but for when tags are used directly).Looks like there are quite a few uses of DesignSystem.tagFor() in Nimble code and a couple references to it in CONTRIBUTING too: github search.