canvas-lms/.gitignore

74 lines
1.3 KiB
Plaintext
Raw Normal View History

2011-02-01 09:57:29 +08:00
.rvmrc
.rdebug_hist
.DS_Store
.powrc
2011-02-01 09:57:29 +08:00
Gemfile.lock
log/*.log
log/*.pid
log/**/*
lib/tasks/deploy.rake
tmp/**/*
tmp/*
db/*.sqlite3
db/*.sqlite3-journal
db/*.sqlite
db/demo
config/GEM_HOME
config/*.yml
js bundle extensions for plugins, bugfixes and DRYification allows plugins to have a bundle get auto-loaded with a corresponding canvas bundle. uses require.js' include mechanism in build.js (when optimized) and a rails helper tweak (when not optimized). this happens automatically based on the path, e.g. the foo plugin's "bundles/extensions/bar" will get automagically included whenever the regular "bar" bundle is required. removes the need for a plugin-level build.js, and auto-generates bundle module definitions in canvas' build.js (via erb). this handles all regular bundles both from canvas and plugins. also fixes plugins so that bundle dependencies get optimized. plugin paths are created automatically, so this means we can remove things like this from plugin bundles and specs: require.config paths: myplugin: "/plugins/myplugin/javascripts" test plan: 1. use canvas in development mode, it should work 2. use canvas in optimized JS mode, it should work i. confirm that all scripts are optimized 3. use canvas in development mode with plugins w/ JS, it should work 4. use canvas in optimized JS mode with plugins w/ JS, it should work i. confirm that all scripts are optimized 5. add a bundle extension in a plugin (e.g. create bundles/extensions/conversations in plugin foo) i. confirm that the extension code runs in development mode ii. confirm that the extension code runs in optimized JS mode Change-Id: If8507afdbabab4ae8966f7db79d9b0e2284034db Reviewed-on: https://gerrit.instructure.com/11238 Tested-by: Jenkins <jenkins@instructure.com> Reviewed-by: Jacob Fugal <jacob@instructure.com>
2012-06-02 07:13:53 +08:00
config/build.js
2011-02-01 09:57:29 +08:00
config/environments/*-local.rb
models.dot
db/*sql
db/development_structure.sql
db/schema.rb
noodle*
tmp_*
public/files/**/*
public/javascripts/cached/*
public/javascripts/translations/*
public/javascripts/compiled/*
public/javascripts/jst/*
2011-02-01 09:57:29 +08:00
public/stylesheets/compiled/*
public/stylesheets/compiled/**/*
public/stylesheets/cached/*
*.pid
vendor/cache/*mswin*.gem
vendor/cache
coverage
instructure_content
.idea/*
exports/*
.sass-cache
.bundle
public/*.gz
public/*/*.gz
public/*/*/*.gz
public/*/*/*/*.gz
public/*/*/*/*/*.gz
public/*/*/*/*/*/*.gz
public/*/*/*/*/*/*/*.gz
public/*/*/*/*/*/*/*/*.gz
public/*/*/*/*/*/*/*/*/*.gz
.*.sw?
2011-02-01 09:57:29 +08:00
public/assets/*
doc/plugins/*
public/doc/api/*
.yardoc/*
spec/javascripts/*Spec.js
spec/javascripts/*/*Spec.js
fix js:test for OSX, plugins, and dynamic manifest no more maintaining spec/javascripts/supports/specs.js to tell the runner which specs to run. instead, the runner is built from an erb that determines the list of specs to run from the filesystem. this new way is also plugin friendly by maintaining a plugin symlink to include plugin specs in the spec/coffeescripts tree. second, give the runner page to the phantomjs execution as a file:/// path rather than just a local path. the latter worked on the build machine, but failed with the phantomjs installed viw macbrew. third, clean up/out some slightly broken specs. * ENVSpec fails when the specs are reordered by the dynamic globbing, but is no longer necessary anyways (since ENV is global now) * the 'specs/helpers/' path in TemplateSpec doesn't work with the new setup, but just 'helpers/' does and is what it should have been using before anyways. * asyncTest is not reliable. once the specs started running in a slightly different order (thanks to the initial point), they started failing with asyncTest race conditions. use fakeTimers and fakeServers instead when appropriate. * found and fixed a minor bug in BackoffPoller while converting/fixing its asyncTests test-plan: - run rake js:test; should run completely as before - add a plugin with a spec in spec_canvas/coffeescripts then run rake js:test again; the plugin's spec should be executed. Change-Id: I9ce5a038829a9e747df26d878ce86dbb7da8c384 Reviewed-on: https://gerrit.instructure.com/9411 Reviewed-by: Jon Jensen <jon@instructure.com> Tested-by: Hudson <hudson@instructure.com>
2012-03-14 07:15:35 +08:00
spec/javascripts/*/*/*Spec.js
spec/javascripts/helpers/
spec/javascripts/plugins/
spec/javascripts/runner.html
AMD Conversion "Trivial" JavaScript / CoffeeScript changes -------------------------------------------------- For the most part, all javascript was simply wrapped in `require` or `define`. The dependencies were found with a script that matched regexes in the files, it errs on the side of listing too many dependencies, so its worth double checking each file's dependencies (over time, anyway). i18n API changes -------------------------------------------------- No longer have to do I18n.scoped calls, just list i18n as a dependency with the scope and it's imported already scoped require ['i18n!some_scope'], (I18n) -> I18n.t 'im_scoped', 'I'm scoped!' JS bundling now done with r.js, not Jammit -------------------------------------------------- We don't use jammit to bundle JS anymore. Simply list dependencies for your JS modules in the file and RequireJS handles the rest. To optimize the JavaScript, first make sure you have node.js 0.4.12+ installed and then run: $ rake js:build The app defaults to the optimized build in production. You can use non-optimized in production by putting ?debug_assets=true in the url just like before. You can also test the optimized JavaScript in development with ?optimized_js=true. Significant changes -------------------------------------------------- These files have "real" changes to them (unlike the JavaScript that is simply wrapped in require and define). Worth taking a really close look at: - app/helpers/application_helper.rb - app/views/layouts/application.html.erb - config/assets.yml - config/build.js - lib/handlebars/handlebars.rb - lib/i18n_extraction/js_extractor.rb - lib/tasks/canvas.rake - lib/tasks/i18n.rake - lib/tasks/js.rake Change-Id: I4bc5ecb1231f331aaded0fef2bcc1f3a9fe482a7 Reviewed-on: https://gerrit.instructure.com/6986 Tested-by: Hudson <hudson@instructure.com> Reviewed-by: Ryan Florence <ryanf@instructure.com>
2011-11-11 00:31:45 +08:00
public/optimized
!node_modules
chromedriver.log
public/plugins/
js bundle extensions for plugins, bugfixes and DRYification allows plugins to have a bundle get auto-loaded with a corresponding canvas bundle. uses require.js' include mechanism in build.js (when optimized) and a rails helper tweak (when not optimized). this happens automatically based on the path, e.g. the foo plugin's "bundles/extensions/bar" will get automagically included whenever the regular "bar" bundle is required. removes the need for a plugin-level build.js, and auto-generates bundle module definitions in canvas' build.js (via erb). this handles all regular bundles both from canvas and plugins. also fixes plugins so that bundle dependencies get optimized. plugin paths are created automatically, so this means we can remove things like this from plugin bundles and specs: require.config paths: myplugin: "/plugins/myplugin/javascripts" test plan: 1. use canvas in development mode, it should work 2. use canvas in optimized JS mode, it should work i. confirm that all scripts are optimized 3. use canvas in development mode with plugins w/ JS, it should work 4. use canvas in optimized JS mode with plugins w/ JS, it should work i. confirm that all scripts are optimized 5. add a bundle extension in a plugin (e.g. create bundles/extensions/conversations in plugin foo) i. confirm that the extension code runs in development mode ii. confirm that the extension code runs in optimized JS mode Change-Id: If8507afdbabab4ae8966f7db79d9b0e2284034db Reviewed-on: https://gerrit.instructure.com/11238 Tested-by: Jenkins <jenkins@instructure.com> Reviewed-by: Jacob Fugal <jacob@instructure.com>
2012-06-02 07:13:53 +08:00
public/javascripts/plugins/
app/coffeescripts/plugins/
app/views/jst/plugins/
app/stylesheets/plugins/
fix js:test for OSX, plugins, and dynamic manifest no more maintaining spec/javascripts/supports/specs.js to tell the runner which specs to run. instead, the runner is built from an erb that determines the list of specs to run from the filesystem. this new way is also plugin friendly by maintaining a plugin symlink to include plugin specs in the spec/coffeescripts tree. second, give the runner page to the phantomjs execution as a file:/// path rather than just a local path. the latter worked on the build machine, but failed with the phantomjs installed viw macbrew. third, clean up/out some slightly broken specs. * ENVSpec fails when the specs are reordered by the dynamic globbing, but is no longer necessary anyways (since ENV is global now) * the 'specs/helpers/' path in TemplateSpec doesn't work with the new setup, but just 'helpers/' does and is what it should have been using before anyways. * asyncTest is not reliable. once the specs started running in a slightly different order (thanks to the initial point), they started failing with asyncTest race conditions. use fakeTimers and fakeServers instead when appropriate. * found and fixed a minor bug in BackoffPoller while converting/fixing its asyncTests test-plan: - run rake js:test; should run completely as before - add a plugin with a spec in spec_canvas/coffeescripts then run rake js:test again; the plugin's spec should be executed. Change-Id: I9ce5a038829a9e747df26d878ce86dbb7da8c384 Reviewed-on: https://gerrit.instructure.com/9411 Reviewed-by: Jon Jensen <jon@instructure.com> Tested-by: Hudson <hudson@instructure.com>
2012-03-14 07:15:35 +08:00
spec/coffeescripts/plugins/
branch_tools.rb
.rbenv-version