-
Notifications
You must be signed in to change notification settings - Fork 791
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
Exception without manifest.js in 4.0.0 #643
Comments
How is the GraphiQL configuring sprockets? It should not be working if the application don't have a manifest because the application manifest need to tell sprockets to link the assets on engines. |
AFAIK it's not configuring anything, it just assumes https://github.com/rmosolgo/graphiql-rails/tree/5770e774f9da754aa8c1eee5651d6c663ca8e2a2/app/assets/javascripts/graphiql/rails |
oh! So I think it will not work anymore unless you add a manifest in your app you could try to remove the initializer that raises locally and see if the javascripts for graphiql are being rendered. |
Redmine 4.0 (<= 4.0.4) and 3.4 (<= 3.4.11) are also affected this issue. I think sprockets 4.0.0 should not raise the error if asset pipeline is disabled ( |
That is disabling assets compilation but not sprockets. If you want to disable sprockets you need to change the |
its not working yet in Rev 18859 |
redmine@redmine:~/redmine-4.0$ bundle exec rake db:migrate RAILS_ENV=production rake aborted! (See full trace by running task with --trace) |
|
@ashrafalzyoud Could you open an issue on https://www.redmine.org/ ? |
Closing since this isn't an issue. Sprockets 4 requires a manifest, of if you don't need sprockets remove it from the application. |
Expected behavior
When no
app/assets/config/manifest.js
file, Sprockets should just warn that it's disabled or could not load, and not throw and error. Since our app doesn't include anything inapp/assets
, and only has Sprockets enabled for the same of the GraphiQL development interface (which does render views and assets but within a gem, not from our app). For this same reason we're not usingconfig.api_only = true
inconfig/application.rb
because that would have disabled Sprockets and prevented this issue from occurring. I believe it's likely why few people caught this issue.Actual behavior
An error is thrown since 4.0, this didn't occur on 3.7.2:
System configuration
The text was updated successfully, but these errors were encountered: