Skip to content
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

Improve spec running (rake, in browser and configurable) #36

Merged
merged 1 commit into from
Feb 24, 2015

Conversation

fkchang
Copy link
Contributor

@fkchang fkchang commented Feb 24, 2015

  • get rake opal:spec task working
  • change default location of specs outside of asset pipeline,
  • handle compilation of files outside of asset pipeline
  • make location configurable
  • update Readme

outside of asset pipeline, handle compilation of files outside of asset
pipeline, make location configurable, update docs
@adambeynon
Copy link
Contributor

I'm keen for this to get merged, but would like @elia thoughts first.

Possibly related to this pull request is a small issue I have had before where requiring "opal" from one of my specs (sometimes indirectly by requiring "application", which then requires "opal") is that I get duplicate file issues because opal-rspec-runner in the first script tag is also requiring the opal runtime.

So, is there a way we can compact everything into one singular sprockets script tag, to avoid any duplicate files? This seems a good time to get a fix on that as well.

elia added a commit that referenced this pull request Feb 24, 2015

Unverified

This commit is not signed, but one or more authors requires that any commit attributed to them is signed.
Improve spec running (rake, in browser and configurable)
@elia elia merged commit f05d36a into opal:master Feb 24, 2015
@elia
Copy link
Member

elia commented Feb 24, 2015

awesome thanks!

@elia
Copy link
Member

elia commented Feb 24, 2015

@adambeynon thinking of replacing the spec controller with a new sprockets env or an opal/builder based rack app

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants