-
Notifications
You must be signed in to change notification settings - Fork 792
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Add deprecations in v3.x" for passing Regexp to sprocket's valid_asset_uri? (string) method #117
Comments
This fixes it but tests are still red: #111 |
Thanks @schneems for the update. I will watch for it to be merged then I will close this as a dup. |
Sorry that was the wrong thing. This should already be in master a61550d Try to update to point at that commit or later, it should be working. However absolute paths in the cache are still broken in master right now. |
FYI: Still seeing the error message and here is the lines inside Gemfile.lock file (after upgrading):
|
Can you give me a full backtrace? Did this work with sprockets 3.2.0? |
Works in the Rails 4.2 version of repo:
The above issue is with the Rails 5.0 version of the repo. Here is the full backtrace (rake 2>&1 output): https://gist.github.com/jasnow/40abdf872082dadf8151 |
Okay, so that's a different issue than the one I linked to earlier. Thanks for the help. Any chance you could give me a small project that reproduces the error, i'll be happy to dig in more. |
Tried sprockets 3.0.0.beta2 version, edge sprockets, and rspec-rails 3.1.0 with Rails 4.2 version of repo and still works. Therefore I will wait until rspec and devise ports to Rails 5. If you wish, I can close this for now and reopen later. |
Seems fine. Thanks for the report |
Here is the specific problem regexp: /bootstrap/glyphicons-halflings-regular.(?:eot|svg|ttf|woff2?)$/ |
Also found this: method_missing in the previous gist: .rvm/gems/[email protected]/bundler/gems/rails-2ceb16e539d1/railties/lib/rails/railtie.rb:194:in `method_missing' |
Found where problem regexp is coming from:
|
I don't think this is a bug in sprockets, but rather a bug in When run with sprockets-rails 2.3.2 we see that regex properly expanded
However in
|
I'm closing this in favor of rails/sprockets-rails#269 it doesn't look like regexs are supported anymore |
OK |
Thanks for the report. |
Wish Github let use transfer an issue from one repo to another. |
They're linked (they can see I linked this issue from that one). You can click "subscribe" on the new issue to get updates. |
Opening since it looks like I need to add deprecations in v3.x |
@schneems - Do you have examples of similar work that someone could look at to do this issue "add deprecations in v3.x"? |
There's no good deprecation framework or pattern here. Sprockets was bad at publically letting people know that things were deprecated. Technically it is already deprecated, but there is no notice. Everything is in the legacy.rb file What I think we want to do is add something like I think that's what we want to do. |
@schneems - Should this still be open? |
@schneems - Thanks for responding. |
@schneems - Are ya'll finished with the above deprecations? |
Haven't really even started. There's definitely more things we can/should deprecated. |
ok |
@schneems - I always knew I was working with a hero - now you have be recognized. Congratulations! |
Is this a thing we still need to do? I now have a deprecation scheme in place in master and we are emitting deprecations. Does someone want to work on this? Can you give me a PR? |
WIP: Passing Regexp to sprocket's valid_asset_uri? (string) method
valid_asset_uri?': undefined method
start_with?' for #Regexp:0xb93ad04 (NoMethodError)Unclear where the regexp input is inserted.
Questions or suggestions are welcome.
The text was updated successfully, but these errors were encountered: