refactor(app, components): enforce strict typing for icon data #20112
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
While we were attempting to type the
IconNameprop forIconas a key oficon-data,icon-dataitself types the keys asstring, so we weren't properly catching lint errors, meaning typing anIconnameprop as "does-not-exist" would pass lint. We were half-working around this by logging an error if the icon name was invalid, but the problem is that this still passes on CI when we could be catching it.To fix, we update the typing to narrow on actual key values in our
icon-data. Seeicon-data.ts.Test Plan and Hands on Testing
Does CI pass?
Risk assessment
very low, just linting updates