expire root TS cache in response to change in referenced .ts files
#24
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
wtmcc
changed the title
.ts files for issue #23.ts files
|
Pinging @gfx |
|
Sorry to be late! LGTM. |
gfx
added a commit
that referenced
this pull request
Mar 25, 2015
expire root TS cache in response to change in referenced `.ts` files
|
👍 |
|
LGTM！！ありがとうございます！ |
|
Awesome, thanks for the merge, @gfx. |
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 PR is intended to fix the undesirable behavior described in issue #23 by the approach I propose there. See that issue for context.
Here, I introduce a step into the TS compiler wrapper that recurses through all referenced files and tells its
Sprockets::Contextthat the TS file being processeddepends_oneach file listed as a reference in the TS idiom.I may have overlooked an easy fix, and Ruby’s not my native language, so feel free to suggest stylistic or other changes! I’m eager to help, and solve our local dev env woes for good. Thanks.
Will