Move importer types into clientlib importer #91690
Merged
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.
This is the last piece of moving all of the importer definitions into a single area
Fixes #90635
Proposed Changes
In #91609, we refactored all of places that define different importers into a single area. As a final step, this moves importer-related types into the same area.
Why are these changes being made?
Previously, there were multiple lists of importers in different places. Having a single source of truth will make it easier to keep track of things and make updates.
Testing Instructions
Since this is just moving
import
definitions around, visual inspections and verifying all of the CI actions pass should be sufficient.However, you could follow the testing instructions in #91609 as an optional, additional check.
Pre-merge Checklist