Fix cyclical type imports relating to color-picker helpers #767
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.
WHY are these changes introduced?
The final cyclical import is dead (again). We can now enable the import/no-cycle eslint rule (again).
#691 removed some cyclical imports. It also stopped exporting a few color helper functions in the final build (see #718) as I incorrectly assumed that they should be internal. It turns out people are using them, so that PR got reverted in #721.
WHAT is this pull request doing?
I reapplied the not-the-color-helper parts of #691 in #754. This PR is the follow up that removes the cyclical dependency in color helpers, without touching any exports.
It moves the color types into the utility folder next to the color utility functions
How to 🎩
yarn run sk type-check
to prove typescript is happyyarn build-consumer web
then runyarn run sk type-check
in web to prove there are no missing exports (You may have to install polaris-icons in web as a workaround because build-consumer isn't smart enough to handle updating transitive dependencies) - web consumes the HSBColor type in some places so this will prove that the types are still exported.