You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Oct 19, 2018. It is now read-only.
currently for webpacker the recommendation is to pull in the client_and_server pack via the layout NOT from within the application.rb tree.
However hyper-spec by default assumes everything you need to run is in the application.js file.
The work around is to use the client_option method to force hyper-spec to use the application.html layout (or any other layout you want really) instead of the layout hyper-spec internally generates (which does not include client_and_server)
Perhaps the solution is to add intelligence about webpacker, but also to make the chunks of code generated by for the automatically generated client to be redefinable in your rspec_helper...
So at least as things change, you can temporarily work around.
currently for webpacker the recommendation is to pull in the client_and_server pack via the layout NOT from within the application.rb tree.
However hyper-spec by default assumes everything you need to run is in the application.js file.
The work around is to use the
client_optionmethod to force hyper-spec to use the application.html layout (or any other layout you want really) instead of the layout hyper-spec internally generates (which does not include client_and_server)Perhaps the solution is to add intelligence about webpacker, but also to make the chunks of code generated by for the automatically generated client to be redefinable in your rspec_helper...
So at least as things change, you can temporarily work around.