Add support for packaging registered files to alternate relative folder #216
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
montegoulding
changed the title
This patch adds support for specifying a `destination` key in registered component files that are to be distributed when packaging. This allows the files to be located outside the app folder during development and then distributed into a relative path when packaged.
montegoulding
force-pushed
the
issue-215
branch
from
f61fdfb to
65a5f3c
Compare
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.
This patch adds support for specifying a
destinationkey in registered component files that are to be distributed when packaging. This allows the files to be located outside the app folder during development and then distributed into a relative path when packaged.Closes #215