These are chat archives for opal/opal
@elia - latest opal-rails-rspec doesn't have the nice list of spec links so you can rerun tests by clicking a link... any way to turn it back on in a config or something?
@catmando it's still WIP, except for the Progress :D
# Patch the RSpec runner to work with Kernel.exit RSpec::Core::Runner.class_eval do def self.autorun at_exit do # see NoCarriageReturnIO source for why this is being done (not on Node though) err, out = get_opal_closed_tty_io # Have to do this in 2 places. This will ensure the default formatter gets the right IO, but need to do this in config for custom formatters # that will be constructed BEFORE this runs, see rspec.rb run(ARGV, err, out).then do |status| exit 0 end end end def self.exit_with_code(code) exit(code) end end
@elia - As you know, I was never a fan of the at_exit stuff. Now that opal-rspec-rails is separate anyways, can a more stock (as in out of the box opal-rspec) approach be used?
I'm fine with it, the main requirement for opal-rspec-rails is that it uses the Rails sprockets env instance because of paths and processors. An other important feature is running in the browser and possibly a CLI as in bin/opal-rails.