Kinda support manifest.compile with simple path

[josh]

Theres been a few issues around Manifest#compile targeting assets using transformers.

• https://github.com/josh/sprockets-es6/issues/9
• Sprockets 3.0.0.rc QA #10 (comment)

The issue has to do with how 2.x and 3.x implement manifest.compile. To support arbitrary procs and fnmatch syntax, sprockets has to iterate over every darn file in the load path to check it against these filters. Its terribly slow. It also works on full path names rather than logical path names. So manifest.compile "application.js" isn't the same as find_asset("application.js"), even though it mostly acts the same. The other times causes these reported bugs.

On 4.x, I removed all the compile magic and made manifest.compile "application.js" just do find_asset("application.js"). Its much simpler and faster but means you can't do this fnmatch stuff anymore.

For 3.x I was just leaving things how they worked on 2.x cause I couldn't really figure out how to still support the 2.x behavior without it. But, I think we can maybe detect if a path passed to compile is "simple" and doesn't use any fnmatch magic and we can just do a direct lookup. I feel like theres some other gotcha to this, but I think it might fix most the causing issues people are actually hitting.

Again, this hacks don't need to stick around in 4.x, this code path is basically deleted. This test case was actually cherry picked from the 4.x branch cause it already works there.

/cc @tricknotes @praxxis @rafaelfranca @lucasmazza

[rafaelfranca]

[lucasmazza]

👍