-
Notifications
You must be signed in to change notification settings - Fork 209
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
Compilation of ui js files #627
Conversation
Cool! Would you want to try refactoring this to use |
And great work!!! |
@jywarren I would like to refactor this to use require() and browserify. I think we can do it in a follow-up PR, will open one soon! Thanks :) |
oh ok! I'm not sure if this will conflict with #562 but I want to merge that first. Thanks, then will merge this. |
So, I don't think we need to include the base library into the UI. We can assume it's there, for now. When we write tests, we may have to include it into the fixture files, as we do in tests for HTML driven code like this: https://github.com/publiclab/PublicLab.Editor/tree/master/spec/javascripts For now, I think we can just compile demo.js and everything in /examples/lib/ into a single file. We may need to restructure how they fit together using |
Hi, I think this is good but perhaps we could integrate this cool idea of having the build process be included in the Travis checks: publiclab/PublicLab.Editor#206 That way we will at least know if the compilation succeeds. How does that sound? Thanks! |
Oh wait, sorry, |
Issue #598
Make sure these boxes are checked before your pull request (PR) is ready to be reviewed and merged. Thanks!
rake test
@publiclab/reviewers
for help, in a comment belowIf tests do fail, click on the red
X
to learn why by reading the logs.Please be sure you've reviewed our contribution guidelines at https://publiclab.org/contributing-to-public-lab-software
Thanks!