With these changes, I'm able to require your CSS / JS base application files without effectively altering my host app's html and body rules. I'm doing that so I can embed GraphiQL in my existing stack with authentication, look-n-feel etc.
As I'm using it
When used normally (nothing changes)
To do this I copied in two files making changes to use our layout.
/controllers/graphiql/rails/editors_controller.rb
/views/graphiql/rails/editors/show.html.erb
Host application.css
*= require graphiql/rails/application
Host application.js
//= require graphiql/rails/application
TLDR;
To avoid requiring versioned CSS files that will cause headaches with graphiql-rails updates, I added a CSS id to increase specificity.
graphiql-rails
tohtml
taghtml
andbody
css rules.With these changes, I'm able to require your CSS / JS base
application
files without effectively altering my host app'shtml
andbody
rules. I'm doing that so I can embed GraphiQL in my existing stack with authentication, look-n-feel etc.To do this I copied in two files making changes to use our layout.
/controllers/graphiql/rails/editors_controller.rb
/views/graphiql/rails/editors/show.html.erb
Host application.css
Host application.js
TLDR;