feat: copy semantic file #1322
Merged
feat: copy semantic file #1322
Conversation
This file contains 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
caspahouzer
reviewed
Mar 26, 2022
caspahouzer
approved these changes
Mar 29, 2022
|
Copied content from https://github.com/tidev/alloy/pull/1322/files into my actual alloy installation and did the test. Test pass. |
hansemannn
approved these changes
Mar 29, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
one part for: tidev/titanium-sdk#13241
copying an existing semantic file when converting classic -> alloy
Test
ti createResources/semantic.colors.jsonor use feat: add default semantic.colors.json titanium-sdk#13326alloy newsemantic.colors.jsonexists inapp/assets/