fix: resolve defs in import-export script (v1.2.2)#12
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Fix the hosted
import-export.shflow so theme imports also resolvedefsreferences when generating the shared Theme Studio URL.Context / Motivation
The previous release fixed named CSS colors and dark-only or light-only theme objects, but the import script still failed for valid theme files that referenced colors through
defsentries.Changes
defsbefore color encoding inpublic/import-export.shdefsreferences with clearer import errors1.2.2Testing
npm run testnpm run lintnpm run buildpublic/import-export.shwith a theme file usingdefs, named colors, and dark-only/light-only token objectsVersion
Patch release:
1.2.2