Sprockets 3 support

[jaredbeck]

It seems that each_file used to yield Pathnames, now yields strings?

I didn't research this very thoroughly, this just seemed like the simplest fix.

There's probably a better way that preserves compat. w/ sprockets 2.

[sonnym]

I definitely want to preserve backwards compatibility, which I think should be pretty easy to accomplish using Pathname#to_s. Something like filepath = ::Pathname.new(filepath_str.to_s) will work with both String and Pathname objects, right?

[jaredbeck]

Something like filepath = ::Pathname.new(filepath_str.to_s) will work with both String and Pathname objects, right?

Sounds good to me. We may want to rename the argument too: filepath_str could be misleading.

[jaredbeck]

As a side note, this is kind of a success story for dynamically typed langs, isn't it, the fact that we can take different data types for an argument. If sprockets were in a strongly typed lang, i wonder how they'd deal. Maybe they would change data types in their API so casually.

[sbleon]

@jaredbeck I'm still getting some failures using this with Sprockets 3. I think we'll need to work on this a bit more.

js-asset_paths was generating an asset hash that lookeds like:

{
  #<Pathname:images/campaign.png>=>"campaign-\x83\xDB\x99\xD6\xA5\xBA\xB5\x11\xAE\x03\x80\xB9\x92\xD5V\x8A\x8C\xBCm\xE7
\xD9\x99\xC0\xAC\xD1+?\x0Fe\xFC\xFF\xE3.png"
}

Note the \x gobbledegook where we should just have hexadecimal strings.

[jaredbeck]

closing due to inactivity