This repository was archived by the owner on Jan 10, 2024. It is now read-only.
Allow passing config yaml file name from environment #172
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hey humans,
It would be great if one could pass a custom yml file instead of the default one. Scenarios include having a separate
application.js
for legacy code and a current one.If you do have a custom yml file then you would simply need to add the environment variable from the console before firing up the test from the web or otherwise.
RAILS_ENV=test JASMINE_CONFIG=jasmine_legacy.yml bundle exec rake spec:javascript
or
JASMINE_CONFIG=jasmine_legacy.yml bundle exec rails server
WDYT?