Skip to content
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

Allow users to skip asset dependency checks #100

Merged

Conversation

schneems
Copy link
Member

Similar to #84 we want to give users the option of not running these tests.

Related but not covered here, the case where an asset in a gem is missing a dependency: schneems/sprockets_better_errors#5

Adding the ability to at least stop the check from occurring would give developers the ability to continue to develop even if a Gem does not update their sprockets dependencies.

@rafaelfranca
Copy link
Member

I think we should document this option in some place

@schneems
Copy link
Member Author

I've added a section in the README. I would like to see an entire Rails guide that is dedicated to all the different config/environment options, how they're used and their common values, but that will require significantly more effort.

Once merged in, I would like set this to true for the default Rails template. Let me know if there are other places I can add documentation.

@rafaelfranca
Copy link
Member

This is not what you want? http://edgeguides.rubyonrails.org/configuring.html

@schneems
Copy link
Member Author

Perfect didn't know that existed, should have spent some time searching first 😲

rafaelfranca added a commit that referenced this pull request Dec 13, 2013
…y-detection

Allow users to skip asset dependency checks
@rafaelfranca rafaelfranca merged commit 25eee98 into rails:master Dec 13, 2013
schneems added a commit to schneems/rails that referenced this pull request Dec 20, 2013
By default `config.assets.raise_runtime_errors` should be set to `true` in development for new apps.

Source: rails/sprockets-rails#100
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants