<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><blockquote type="cite" style="-webkit-tap-highlight-color: rgba(26, 26, 26, 0.296875); -webkit-composition-fill-color: rgba(175, 192, 227, 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.230469); "><div dir="ltr"><div class="gmail_quote"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">I'm not sure how to do this, and Rails 4 seems to have a bunch of stuff hard-coded that's not configurable (e.g. it minifies code in production but not development and none of the config flags for this change anything). Where are the docs?</div></div></div></div></div></blockquote><div><br></div>Rather than messing with the digests themselves you could use the manifest.json file to find the fingerprinted asset names from the the filenames. The only problem being that the manifest.json file is also fingerprinted... It's generated after rake assets:precompile in public/assets</div><div><br></div><div>George<br><br></div><div>On 31 Jul 2013, at 15:05, James Coglan <<a href="mailto:jcoglan@gmail.com">jcoglan@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr"><span style="color:rgb(80,0,80)">On 31 July 2013 11:34, Murray Steele </span><span dir="ltr" style="color:rgb(80,0,80)"><<a href="mailto:murray.steele@gmail.com" target="_blank">murray.steele@gmail.com</a>></span><span style="color:rgb(80,0,80)"> wrote:</span><br>
<div class="gmail_quote"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div class="im">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Could you customise the digest mechanism in sprockets to produce empty (or knowable) digest suffixes. Of course, you'd only want this for the JS test run, so you're not testing your exact production files, but you're testing something very close to it.</div>
</blockquote><div><br></div></div><div>I'm not sure how to do this, and Rails 4 seems to have a bunch of stuff hard-coded that's not configurable (e.g. it minifies code in production but not development and none of the config flags for this change anything). Where are the docs?</div>
<div class="im">
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Alternatively, could you asset compile the JS test harness so that it has the digested asset names in it?</div>
</div></blockquote><div><br></div></div><div>That's not a bad idea, and will work with a few test runners. Compile the code and tests into one static JS file, stick it on a web page, and have it run. Still probably requires the build target to have a stable un-digest-ed name in order to be easy to use. Or, you could run `cat public/assets/test-*.js > public/assets/test.js` after compiling.</div>
</div></div></div></div></div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>Chat mailing list</span><br><span><a href="mailto:Chat@lists.lrug.org">Chat@lists.lrug.org</a></span><br><span><a href="http://lists.lrug.org/listinfo.cgi/chat-lrug.org">http://lists.lrug.org/listinfo.cgi/chat-lrug.org</a></span><br></div></blockquote></body></html>