ylqjgm
/
canvas-lms
mirror of https://github.com/instructure/canvas-lms.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
canvas-lms/.gitignore

69 lines
1.5 KiB
Plaintext
Raw Normal View History

clean up .gitignore remove a lot of things that are no longer relevant, DRY it up a bit and make it a bit more explicit (root paths, better globbing) test plan: 1. `git status` 2. all your previously ignored stuff should still be ignored, except perhaps editor stuff, which should really go in .git/info/exclude Change-Id: I0c0f6dc3cd969bb6f90f26c1af83f1bd7ef852e4 Reviewed-on: https://gerrit.instructure.com/16994 Reviewed-by: Joe Tanner <joe@instructure.com> Tested-by: Jenkins <jenkins@instructure.com> QA-Review: Jon Jensen <jon@instructure.com>
2013-01-22 01:16:29 +08:00
# What goes in this file:
# * local canvas configuration (db, ymls, overrides, etc.)
# * generated/cached stuff (docs, css, js, uploads, etc.)
#
# What does NOT go in this file
# * editor-related stuff
# * random scripts only used by you
# * env-specific stuff (e.g. .DS_Store)
# * pretty much any dotfile not already covered (e.g. .rvmrc)
#
# That's what .git/info/exclude and core.excludesfile are for :)
ignore all .bundle folders and Gemfile.lock Change-Id: Ib78461b98a15d81812d04bcdbc7e2dbd0320b979 Reviewed-on: https://gerrit.instructure.com/29508 Tested-by: Jenkins <jenkins@instructure.com> Reviewed-by: Raphael Weiner <rweiner@pivotallabs.com> Product-Review: Raphael Weiner <rweiner@pivotallabs.com> QA-Review: Raphael Weiner <rweiner@pivotallabs.com>
2014-02-01 07:52:04 +08:00
.bundle/
clean up .gitignore remove a lot of things that are no longer relevant, DRY it up a bit and make it a bit more explicit (root paths, better globbing) test plan: 1. `git status` 2. all your previously ignored stuff should still be ignored, except perhaps editor stuff, which should really go in .git/info/exclude Change-Id: I0c0f6dc3cd969bb6f90f26c1af83f1bd7ef852e4 Reviewed-on: https://gerrit.instructure.com/16994 Reviewed-by: Joe Tanner <joe@instructure.com> Tested-by: Jenkins <jenkins@instructure.com> QA-Review: Jon Jensen <jon@instructure.com>
2013-01-22 01:16:29 +08:00
/.yardoc/
ignore ember app main files Change-Id: I67ccff84f9f73194b3f6a070c23685fdc9d7b6a4 Reviewed-on: https://gerrit.instructure.com/24156 Tested-by: Jenkins <jenkins@instructure.com> Reviewed-by: Mark Ericksen <marke@instructure.com> Reviewed-by: Jon Jensen <jon@instructure.com> Product-Review: Ryan Florence <ryanf@instructure.com> QA-Review: Ryan Florence <ryanf@instructure.com>
2013-09-07 04:16:57 +08:00
/app/coffeescripts/ember/*/main.coffee
implemented dress_code also added styles to make .form-controls look good in dialogs. closes #CNVS-4302 Change-Id: Ibe54ee4046ac255b0b0ea83d32afc88e4a820464 Reviewed-on: https://gerrit.instructure.com/19331 Tested-by: Jenkins <jenkins@instructure.com> Reviewed-by: Jon Jensen <jon@instructure.com> QA-Review: Ryan Florence <ryanf@instructure.com> Product-Review: Ryan Florence <ryanf@instructure.com>
2013-03-20 00:58:55 +08:00
/app/views/info/styleguide.html.erb
clean up .gitignore remove a lot of things that are no longer relevant, DRY it up a bit and make it a bit more explicit (root paths, better globbing) test plan: 1. `git status` 2. all your previously ignored stuff should still be ignored, except perhaps editor stuff, which should really go in .git/info/exclude Change-Id: I0c0f6dc3cd969bb6f90f26c1af83f1bd7ef852e4 Reviewed-on: https://gerrit.instructure.com/16994 Reviewed-by: Joe Tanner <joe@instructure.com> Tested-by: Jenkins <jenkins@instructure.com> QA-Review: Jon Jensen <jon@instructure.com>
2013-01-22 01:16:29 +08:00
/config/*.yml
A way for devs to set their own brand style vars closes: CNVS-17331 CNVS-14993 refs: CNVS-17332 This is the first step to having a full theme editor where accounts can pick their own color scheme in a UI and all of canvas will be branded to their school colors. test plan: * copy config/brand_variables.scss.example to config/brand_variables.scss * recompile sass * users in accounts that have "new styles" or "k12" turned on that have not turned on "high contrast". should see a new purple-orange canvas. * but users that have turned on the "high_contrast" feature or accounts that have not turned on either "k12" or "new styles" should not. Change-Id: I16342d43b56e49d52fbee8fa5c6a0fd57ae6e602 Reviewed-on: https://gerrit.instructure.com/46085 Tested-by: Jenkins <jenkins@instructure.com> Reviewed-by: Jacob Fugal <jacob@instructure.com> QA-Review: Jeremy Putnam <jeremyp@instructure.com> Product-Review: Colleen Palmer <colleen@instructure.com>
2014-12-19 07:36:25 +08:00
/config/brand_variables.scss
clean up .gitignore remove a lot of things that are no longer relevant, DRY it up a bit and make it a bit more explicit (root paths, better globbing) test plan: 1. `git status` 2. all your previously ignored stuff should still be ignored, except perhaps editor stuff, which should really go in .git/info/exclude Change-Id: I0c0f6dc3cd969bb6f90f26c1af83f1bd7ef852e4 Reviewed-on: https://gerrit.instructure.com/16994 Reviewed-by: Joe Tanner <joe@instructure.com> Tested-by: Jenkins <jenkins@instructure.com> QA-Review: Jon Jensen <jon@instructure.com>
2013-01-22 01:16:29 +08:00
/config/build.js
/config/environments/*-local.rb
don't keep generated locales in git closes CNVS-12609 test plan: - make sure rake i18n:generate still works - basic regression of i18n in canvas Change-Id: I882c7b6f197d65aa673a22225ae6a87ee4431aa0 Reviewed-on: https://gerrit.instructure.com/33760 Tested-by: Jenkins <jenkins@instructure.com> Reviewed-by: Jon Jensen <jon@instructure.com> QA-Review: Amber Taniuchi <amber@instructure.com> Product-Review: Simon Williams <simon@instructure.com>
2014-04-24 00:57:32 +08:00
/config/locales/generated/
i18nliner-js (part I) this swaps out our "parsing" with i18nliner-js also remove localization abilities of I18n.beforeLabel, since it's not worth the trouble to support. it can still be called to format a string. notable changes/fixes in generated yml: 1. client_apps are picked up by i18n:rake so they'll get translated... due to the old short-circuiting logic (`rc = rc && ...`), it would stop processing scripts within a particular file after the first one it found without an I18n.t 2. we no longer incorrectly double-escape special chars in our js strings (e.g. newlines are actually newlines, not a literal "\n") test plan: 1. verify string extraction: 1. `rake js:generate i18n:generate` before and after this commit 2. confirm `config/locales/generated/en.yml` is identical, except the notable changes/fixes listed above 2. verify js translation file generation: 1. `rake i18n:generate_js` before and after this commit 2. confirm the files in public/javascripts/translations are identical 3. verify client_app checker still works: 1. `cd client_apps/canvas_quiz_statistics/` 2. `grunt check_i18n` Change-Id: Ic8ad058bee1c9476f42916f10b612c1c08863fe3 Reviewed-on: https://gerrit.instructure.com/42809 Reviewed-by: Michael Ziwisky <mziwisky@instructure.com> Product-Review: Michael Ziwisky <mziwisky@instructure.com> QA-Review: Michael Ziwisky <mziwisky@instructure.com> Tested-by: Jenkins <jenkins@instructure.com>
2014-10-16 02:50:10 +08:00
/config/RAILS4
add some ignores Change-Id: I5169e13d1df329fccf9369a4130033956be7cc90 Reviewed-on: https://gerrit.instructure.com/50061 Tested-by: Jenkins Reviewed-by: Rob Orton <rob@instructure.com> Product-Review: Cody Cutrer <cody@instructure.com> QA-Review: Cody Cutrer <cody@instructure.com>
2015-03-10 03:34:59 +08:00
/coverage/
clean up .gitignore remove a lot of things that are no longer relevant, DRY it up a bit and make it a bit more explicit (root paths, better globbing) test plan: 1. `git status` 2. all your previously ignored stuff should still be ignored, except perhaps editor stuff, which should really go in .git/info/exclude Change-Id: I0c0f6dc3cd969bb6f90f26c1af83f1bd7ef852e4 Reviewed-on: https://gerrit.instructure.com/16994 Reviewed-by: Joe Tanner <joe@instructure.com> Tested-by: Jenkins <jenkins@instructure.com> QA-Review: Jon Jensen <jon@instructure.com>
2013-01-22 01:16:29 +08:00
/db/schema.rb
/db/*.sqlite*
/db/*sql
/exports/
ignore all .bundle folders and Gemfile.lock Change-Id: Ib78461b98a15d81812d04bcdbc7e2dbd0320b979 Reviewed-on: https://gerrit.instructure.com/29508 Tested-by: Jenkins <jenkins@instructure.com> Reviewed-by: Raphael Weiner <rweiner@pivotallabs.com> Product-Review: Raphael Weiner <rweiner@pivotallabs.com> QA-Review: Raphael Weiner <rweiner@pivotallabs.com>
2014-02-01 07:52:04 +08:00
Gemfile.lock
add springified binstubs also switch rails3 lockfile to the default, so the spring binstub can use the default lockfile and see itself Change-Id: Id10cbc3df010671a59c73137a77583e2c2e0e5a8 Reviewed-on: https://gerrit.instructure.com/37802 Tested-by: Jenkins <jenkins@instructure.com> Reviewed-by: Cameron Sutter <csutter@instructure.com> Product-Review: Cody Cutrer <cody@instructure.com> QA-Review: Cody Cutrer <cody@instructure.com>
2014-07-17 23:52:07 +08:00
Gemfile.lock2
rails3: updated .gitignore Change-Id: I2af3335578140c943b962dee7fa506bba62948d3 Reviewed-on: https://gerrit.instructure.com/32171 Reviewed-by: James Williams <jamesw@instructure.com> Tested-by: Jenkins <jenkins@instructure.com> Product-Review: Simon Williams <simon@instructure.com> QA-Review: Simon Williams <simon@instructure.com>
2014-03-20 12:27:41 +08:00
Gemfile.lock3
begin rails 4 enough for bundle install to work with 4.1.5 Change-Id: I277df9e4315fa250b6028139113c74721148e2f0 Reviewed-on: https://gerrit.instructure.com/39656 Reviewed-by: Brian Palmer <brianp@instructure.com> Tested-by: Jenkins <jenkins@instructure.com> Product-Review: Cody Cutrer <cody@instructure.com> QA-Review: Cody Cutrer <cody@instructure.com>
2014-07-02 02:32:06 +08:00
Gemfile.lock4
clean up .gitignore remove a lot of things that are no longer relevant, DRY it up a bit and make it a bit more explicit (root paths, better globbing) test plan: 1. `git status` 2. all your previously ignored stuff should still be ignored, except perhaps editor stuff, which should really go in .git/info/exclude Change-Id: I0c0f6dc3cd969bb6f90f26c1af83f1bd7ef852e4 Reviewed-on: https://gerrit.instructure.com/16994 Reviewed-by: Joe Tanner <joe@instructure.com> Tested-by: Jenkins <jenkins@instructure.com> QA-Review: Jon Jensen <jon@instructure.com>
2013-01-22 01:16:29 +08:00
/log/
i18nliner-js (part I) this swaps out our "parsing" with i18nliner-js also remove localization abilities of I18n.beforeLabel, since it's not worth the trouble to support. it can still be called to format a string. notable changes/fixes in generated yml: 1. client_apps are picked up by i18n:rake so they'll get translated... due to the old short-circuiting logic (`rc = rc && ...`), it would stop processing scripts within a particular file after the first one it found without an I18n.t 2. we no longer incorrectly double-escape special chars in our js strings (e.g. newlines are actually newlines, not a literal "\n") test plan: 1. verify string extraction: 1. `rake js:generate i18n:generate` before and after this commit 2. confirm `config/locales/generated/en.yml` is identical, except the notable changes/fixes listed above 2. verify js translation file generation: 1. `rake i18n:generate_js` before and after this commit 2. confirm the files in public/javascripts/translations are identical 3. verify client_app checker still works: 1. `cd client_apps/canvas_quiz_statistics/` 2. `grunt check_i18n` Change-Id: Ic8ad058bee1c9476f42916f10b612c1c08863fe3 Reviewed-on: https://gerrit.instructure.com/42809 Reviewed-by: Michael Ziwisky <mziwisky@instructure.com> Product-Review: Michael Ziwisky <mziwisky@instructure.com> QA-Review: Michael Ziwisky <mziwisky@instructure.com> Tested-by: Jenkins <jenkins@instructure.com>
2014-10-16 02:50:10 +08:00
/node_modules
upgrade coffee-script to 1.6.2 test plan: - make sure you have the coffee binary from npm: `npm install -g coffee-script@1.6.2` - run rake js:generate, make sure all coffeescript still compiles correctly - open a coffeescript file and make sure it still gets automatically compiled when saved by guard. - rejoice at the arrival of source maps. Change-Id: I06ce9e83a76be9d4cc0e2b2c80566a0db19f9d7e Reviewed-on: https://gerrit.instructure.com/18842 Tested-by: Jenkins <jenkins@instructure.com> Reviewed-by: Ryan Florence <ryanf@instructure.com> Product-Review: Stanley Stuart <stanley@instructure.com> QA-Review: Stanley Stuart <stanley@instructure.com>
2013-03-21 12:11:41 +08:00
/public/app/
clean up .gitignore remove a lot of things that are no longer relevant, DRY it up a bit and make it a bit more explicit (root paths, better globbing) test plan: 1. `git status` 2. all your previously ignored stuff should still be ignored, except perhaps editor stuff, which should really go in .git/info/exclude Change-Id: I0c0f6dc3cd969bb6f90f26c1af83f1bd7ef852e4 Reviewed-on: https://gerrit.instructure.com/16994 Reviewed-by: Joe Tanner <joe@instructure.com> Tested-by: Jenkins <jenkins@instructure.com> QA-Review: Jon Jensen <jon@instructure.com>
2013-01-22 01:16:29 +08:00
/public/assets/
/public/doc/api/
/public/javascripts/compiled/
/public/javascripts/jst/
added jsx Change-Id: Ia23b8f3f7b3d6300f185548ad8c7a63541e7f795 Reviewed-on: https://gerrit.instructure.com/43784 Reviewed-by: Jason Madsen <jmadsen@instructure.com> Tested-by: Jenkins <jenkins@instructure.com> Product-Review: Ryan Florence <ryanf@instructure.com> QA-Review: Ryan Florence <ryanf@instructure.com>
2014-10-10 06:56:09 +08:00
/public/javascripts/jsx/
clean up .gitignore remove a lot of things that are no longer relevant, DRY it up a bit and make it a bit more explicit (root paths, better globbing) test plan: 1. `git status` 2. all your previously ignored stuff should still be ignored, except perhaps editor stuff, which should really go in .git/info/exclude Change-Id: I0c0f6dc3cd969bb6f90f26c1af83f1bd7ef852e4 Reviewed-on: https://gerrit.instructure.com/16994 Reviewed-by: Joe Tanner <joe@instructure.com> Tested-by: Jenkins <jenkins@instructure.com> QA-Review: Jon Jensen <jon@instructure.com>
2013-01-22 01:16:29 +08:00
/public/javascripts/translations/
/public/optimized/
a way for accounts to opt-in to new styles and users to high-contrast fixes CNVS-11426 The UI/UX team *really* wants to start doing some major style changes to the canvas interface. Because it is a very visual change and especially because we've let people hack the crap out of canvas styles with their own css override file, any changes we do need to be behind a feature flag so an institution can opt-in when they are ready. This commit does some trickery so we actually create 4 different versions of every stylesheet. one for each variant in: legacy_normal_contrast legacy_high_contrast new_styles_normal_contrast new_styles_high_contrast and then sets the $use_new_styles and $use_high_contrast sass variables accordingly in each. now, in any sass file, you can do things like: @if $use_new_styles { background-color: red; } @else { background-color: blue; } @if not $use_high_contrast{ font-size: 12px; } test plan: * in a production (minified assets) environment, ensure you see: <link href="/assets/common_legacy_normal_contrast.css... in the <head> of the page * go to the account settings page for the domain_root_account you are on * turn on the "Use New Styles" feature * now verify that <link href="/assets/common_new_styles_normal_contrast.css... is in the <head>. There should not be any visible differences because we do not have any styles that target specifically $use_new_styles yet. * now, go to /settings and turn on the user feature for "Use High Contrast Styles" * verify that <link href="/assets/common_new_styles_high_contrast.css.. is in the <head> * again, turning that on will not actually change the way anything looks, the next commit (g/32863) will take care of that Change-Id: I45ba4ddfe780c5c819fb995b61ebfc0a5325d418 Reviewed-on: https://gerrit.instructure.com/31881 Tested-by: Jenkins <jenkins@instructure.com> Reviewed-by: Ryan Shaw <ryan@instructure.com> Product-Review: Ryan Shaw <ryan@instructure.com> QA-Review: Ryan Shaw <ryan@instructure.com> Reviewed-by: Bracken Mosbacker <bracken@instructure.com>
2014-04-03 14:37:18 +08:00
/public/stylesheets_compiled/
i18nliner-js (part I) this swaps out our "parsing" with i18nliner-js also remove localization abilities of I18n.beforeLabel, since it's not worth the trouble to support. it can still be called to format a string. notable changes/fixes in generated yml: 1. client_apps are picked up by i18n:rake so they'll get translated... due to the old short-circuiting logic (`rc = rc && ...`), it would stop processing scripts within a particular file after the first one it found without an I18n.t 2. we no longer incorrectly double-escape special chars in our js strings (e.g. newlines are actually newlines, not a literal "\n") test plan: 1. verify string extraction: 1. `rake js:generate i18n:generate` before and after this commit 2. confirm `config/locales/generated/en.yml` is identical, except the notable changes/fixes listed above 2. verify js translation file generation: 1. `rake i18n:generate_js` before and after this commit 2. confirm the files in public/javascripts/translations are identical 3. verify client_app checker still works: 1. `cd client_apps/canvas_quiz_statistics/` 2. `grunt check_i18n` Change-Id: Ic8ad058bee1c9476f42916f10b612c1c08863fe3 Reviewed-on: https://gerrit.instructure.com/42809 Reviewed-by: Michael Ziwisky <mziwisky@instructure.com> Product-Review: Michael Ziwisky <mziwisky@instructure.com> QA-Review: Michael Ziwisky <mziwisky@instructure.com> Tested-by: Jenkins <jenkins@instructure.com>
2014-10-16 02:50:10 +08:00
/spec/javascripts/compiled/
/spec/javascripts/requirejs_config.js
move compiled coffeescript specs to specs/javascipts/compiled test plan: - run "rm -rf spec/javascripts; git checkout HEAD -- specs/javascripts" to reset your compiled javascript tests. - run rake js:generate_runner - JS tests should pass - # of JS tests should be the same as they are on master before this commit Change-Id: I936aec8a8a5e2cc739e09757c622f300e99c72ef Reviewed-on: https://gerrit.instructure.com/25615 Tested-by: Jenkins <jenkins@instructure.com> Reviewed-by: Jon Jensen <jon@instructure.com> Product-Review: Bryan Madsen <bryan@instructure.com> QA-Review: Bryan Madsen <bryan@instructure.com>
2013-10-25 04:37:48 +08:00
/spec/javascripts/runner.html
clean up JS tests and integrate karma - js:generate_runner now generates common files to be used by different test runners - js spec file order now shuffled to better expose dependencies - fakeENV now returns two methods: setup and teardown - stock tinymce 3 files are now wrapped for AMD test plan: - tinymce should work the same - js:test rake task should run tests - js:build task should work as normal (using new location of r.js) - test results should successfully send to firework Change-Id: Ic09647f55dae57130fa0fe3d6a9168d2b67b89a2 Reviewed-on: https://gerrit.instructure.com/29297 QA-Review: Shawn Meredith <shawn@instructure.com> Tested-by: Shawn Meredith <shawn@instructure.com> Tested-by: Aaron Shafovaloff <ashafovaloff@instructure.com> Reviewed-by: Aaron Shafovaloff <ashafovaloff@instructure.com> Product-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com>
2014-01-24 23:58:37 +08:00
/spec/javascripts/tests.js
clean up .gitignore remove a lot of things that are no longer relevant, DRY it up a bit and make it a bit more explicit (root paths, better globbing) test plan: 1. `git status` 2. all your previously ignored stuff should still be ignored, except perhaps editor stuff, which should really go in .git/info/exclude Change-Id: I0c0f6dc3cd969bb6f90f26c1af83f1bd7ef852e4 Reviewed-on: https://gerrit.instructure.com/16994 Reviewed-by: Joe Tanner <joe@instructure.com> Tested-by: Jenkins <jenkins@instructure.com> QA-Review: Jon Jensen <jon@instructure.com>
2013-01-22 01:16:29 +08:00
/tmp/
start adding rails 3.0 support This can successfully load rails console and rails server. There are many, many problems still. The idea is this won't change anything under rails 2.3, it's all backwards compatible. closes CNVS-4711 test plan: `touch RAILS3` in your Canvas Rails.root directory. The run `bundle update` and verify that you get rails 3 installed. Run `bundle exec rails c` to load console or `bundle exec rails s` to start a webrick server. You can login, though the dashboard currently breaks. Also jammit isn't working yet. But more importantly, Rails 2.3 should still work same as ever. All tests should pass, and a basic regression sanity check would be good too. Change-Id: Idd6f35de88adde84cd2db3a650f44b71bd6e9684 Reviewed-on: https://gerrit.instructure.com/18453 Reviewed-by: Brian Palmer <brianp@instructure.com> Tested-by: Jenkins <jenkins@instructure.com> QA-Review: Clare Hetherington <clare@instructure.com> Product-Review: Bracken Mosbacker <bracken@instructure.com>
2013-03-21 04:30:20 +08:00
/vendor/plugins/rails_upgrade
Takes out a npm-debug.log file that got in the repo and adds it to the gitignore file Change-Id: Ic17f80370a000ed3e9800a5d9fb9a0547a30cde9 Reviewed-on: https://gerrit.instructure.com/47782 Reviewed-by: Benjamin Porter <bporter@instructure.com> Product-Review: Colleen Palmer <colleen@instructure.com> Reviewed-by: Jacob Fugal <jacob@instructure.com> QA-Review: Jacob Fugal <jacob@instructure.com> Tested-by: Colleen Palmer <colleen@instructure.com>
2015-01-24 07:40:01 +08:00
npm-debug.log
clean up .gitignore remove a lot of things that are no longer relevant, DRY it up a bit and make it a bit more explicit (root paths, better globbing) test plan: 1. `git status` 2. all your previously ignored stuff should still be ignored, except perhaps editor stuff, which should really go in .git/info/exclude Change-Id: I0c0f6dc3cd969bb6f90f26c1af83f1bd7ef852e4 Reviewed-on: https://gerrit.instructure.com/16994 Reviewed-by: Joe Tanner <joe@instructure.com> Tested-by: Jenkins <jenkins@instructure.com> QA-Review: Jon Jensen <jon@instructure.com>
2013-01-22 01:16:29 +08:00
# generated plugin stuff
/app/coffeescripts/plugins/
/app/stylesheets/plugins/
/app/views/jst/plugins/
/public/javascripts/plugins/
/public/plugins/
/spec/coffeescripts/plugins/
move compiled coffeescript specs to specs/javascipts/compiled test plan: - run "rm -rf spec/javascripts; git checkout HEAD -- specs/javascripts" to reset your compiled javascript tests. - run rake js:generate_runner - JS tests should pass - # of JS tests should be the same as they are on master before this commit Change-Id: I936aec8a8a5e2cc739e09757c622f300e99c72ef Reviewed-on: https://gerrit.instructure.com/25615 Tested-by: Jenkins <jenkins@instructure.com> Reviewed-by: Jon Jensen <jon@instructure.com> Product-Review: Bryan Madsen <bryan@instructure.com> QA-Review: Bryan Madsen <bryan@instructure.com>
2013-10-25 04:37:48 +08:00
/spec/plugins/
add ember-qunit for ember unit tests closes CNVS-11294 test plan: - enable ember quizzes - ensure that existing ember quizzes continue to work - all existing ember tests should continue to pass Change-Id: I4f56b1267504533be8332520ea5f77d2fa566263 Reviewed-on: https://gerrit.instructure.com/33105 Reviewed-by: Derek DeVries <ddevries@instructure.com> Tested-by: Jenkins <jenkins@instructure.com> QA-Review: Caleb Guanzon <cguanzon@instructure.com> Product-Review: Jason Madsen <jmadsen@instructure.com>
2014-04-10 04:41:41 +08:00
i18nliner-js (part I) this swaps out our "parsing" with i18nliner-js also remove localization abilities of I18n.beforeLabel, since it's not worth the trouble to support. it can still be called to format a string. notable changes/fixes in generated yml: 1. client_apps are picked up by i18n:rake so they'll get translated... due to the old short-circuiting logic (`rc = rc && ...`), it would stop processing scripts within a particular file after the first one it found without an I18n.t 2. we no longer incorrectly double-escape special chars in our js strings (e.g. newlines are actually newlines, not a literal "\n") test plan: 1. verify string extraction: 1. `rake js:generate i18n:generate` before and after this commit 2. confirm `config/locales/generated/en.yml` is identical, except the notable changes/fixes listed above 2. verify js translation file generation: 1. `rake i18n:generate_js` before and after this commit 2. confirm the files in public/javascripts/translations are identical 3. verify client_app checker still works: 1. `cd client_apps/canvas_quiz_statistics/` 2. `grunt check_i18n` Change-Id: Ic8ad058bee1c9476f42916f10b612c1c08863fe3 Reviewed-on: https://gerrit.instructure.com/42809 Reviewed-by: Michael Ziwisky <mziwisky@instructure.com> Product-Review: Michael Ziwisky <mziwisky@instructure.com> QA-Review: Michael Ziwisky <mziwisky@instructure.com> Tested-by: Jenkins <jenkins@instructure.com>
2014-10-16 02:50:10 +08:00
# generated client app stuff
client app: canvas_quiz_statistics This commit brings in canvas_quiz_statistics, a client app that can be embedded in Canvas. Closes CNVS-14781, CNVS-14846, CNVS-14847, CNVS-14850 > What's done - full build integration, meaning the app runs with ?optimized_js=1: + JavaScript "built" source gets piped into the r.js build pipeline like any other Canvas JS source in public/javascripts/* + SCSS sources get picked up by the sass-compiler like Canvas style sources and they get compiled from the grounds-up + I18n: phrases are extracted properly, with default values and options, by our i18n rake tasks - new rake task js:build_client_apps that builds client apps and injects them as input to the rest of the JS build process - support for using Canvas JS packages, like d3, jQuery, and Backbone - support for using Canvas SASS variables & helpers - super i18n support: use raw I18n.t() calls like you are in Canvas, with development-time interpolation, as well as super new Handlebars-like block-style translations in React, perfect for very long phrases (mini-articles) > Docs and References The code was originally developed in its own github repository. While I won't be pushing code to that repo anymore, the Wiki will still house the docs until we find a better place. - Repo: https://github.com/amireh/canvas_quiz_statistics - Development guide: http://bit.ly/1sNOhER - Integration guide: http://bit.ly/1m9kA9V > TESTING - login as a teacher - go to /courses/:course_id/quizzes/:quiz_id/statistics_cqs + make sure you see something that looks like the Ember stats + click one of those little "?" help icons, you get a dialog: - verify the contents within the dialog are actual English text, not code gibberish - there's also a link at the end of that dialog, click it and verify it takes you to an Instructure help article - build the assets: `bundle exec rake canvas:compile_assets` then: + add ?optimized_js=1 to the URL and reload the page: - verify the app still works Change-Id: Ic474650dfb06a1c22869ed9680dd04d1ca0f651d Reviewed-on: https://gerrit.instructure.com/39105 Tested-by: Jenkins <jenkins@instructure.com> Reviewed-by: Hannah Bottalla <hannah@instructure.com> Reviewed-by: Adam Ard <aard@instructure.com> QA-Review: Trevor deHaan <tdehaan@instructure.com> Product-Review: Ahmad Amireh <ahmad@instructure.com>
2014-08-06 15:04:23 +08:00
/public/javascripts/client_apps/
i18nliner-js (part I) this swaps out our "parsing" with i18nliner-js also remove localization abilities of I18n.beforeLabel, since it's not worth the trouble to support. it can still be called to format a string. notable changes/fixes in generated yml: 1. client_apps are picked up by i18n:rake so they'll get translated... due to the old short-circuiting logic (`rc = rc && ...`), it would stop processing scripts within a particular file after the first one it found without an I18n.t 2. we no longer incorrectly double-escape special chars in our js strings (e.g. newlines are actually newlines, not a literal "\n") test plan: 1. verify string extraction: 1. `rake js:generate i18n:generate` before and after this commit 2. confirm `config/locales/generated/en.yml` is identical, except the notable changes/fixes listed above 2. verify js translation file generation: 1. `rake i18n:generate_js` before and after this commit 2. confirm the files in public/javascripts/translations are identical 3. verify client_app checker still works: 1. `cd client_apps/canvas_quiz_statistics/` 2. `grunt check_i18n` Change-Id: Ic8ad058bee1c9476f42916f10b612c1c08863fe3 Reviewed-on: https://gerrit.instructure.com/42809 Reviewed-by: Michael Ziwisky <mziwisky@instructure.com> Product-Review: Michael Ziwisky <mziwisky@instructure.com> QA-Review: Michael Ziwisky <mziwisky@instructure.com> Tested-by: Jenkins <jenkins@instructure.com>
2014-10-16 02:50:10 +08:00
# remove this once we move jquery into bower
add ember-qunit for ember unit tests closes CNVS-11294 test plan: - enable ember quizzes - ensure that existing ember quizzes continue to work - all existing ember tests should continue to pass Change-Id: I4f56b1267504533be8332520ea5f77d2fa566263 Reviewed-on: https://gerrit.instructure.com/33105 Reviewed-by: Derek DeVries <ddevries@instructure.com> Tested-by: Jenkins <jenkins@instructure.com> QA-Review: Caleb Guanzon <cguanzon@instructure.com> Product-Review: Jason Madsen <jmadsen@instructure.com>
2014-04-10 04:41:41 +08:00
/public/javascripts/bower/jquery/
i18nliner-js (part I) this swaps out our "parsing" with i18nliner-js also remove localization abilities of I18n.beforeLabel, since it's not worth the trouble to support. it can still be called to format a string. notable changes/fixes in generated yml: 1. client_apps are picked up by i18n:rake so they'll get translated... due to the old short-circuiting logic (`rc = rc && ...`), it would stop processing scripts within a particular file after the first one it found without an I18n.t 2. we no longer incorrectly double-escape special chars in our js strings (e.g. newlines are actually newlines, not a literal "\n") test plan: 1. verify string extraction: 1. `rake js:generate i18n:generate` before and after this commit 2. confirm `config/locales/generated/en.yml` is identical, except the notable changes/fixes listed above 2. verify js translation file generation: 1. `rake i18n:generate_js` before and after this commit 2. confirm the files in public/javascripts/translations are identical 3. verify client_app checker still works: 1. `cd client_apps/canvas_quiz_statistics/` 2. `grunt check_i18n` Change-Id: Ic8ad058bee1c9476f42916f10b612c1c08863fe3 Reviewed-on: https://gerrit.instructure.com/42809 Reviewed-by: Michael Ziwisky <mziwisky@instructure.com> Product-Review: Michael Ziwisky <mziwisky@instructure.com> QA-Review: Michael Ziwisky <mziwisky@instructure.com> Tested-by: Jenkins <jenkins@instructure.com>
2014-10-16 02:50:10 +08:00
# canvas-gems
Quiz Stats [Backend] - Gem & Essays Refactoring the generation of quiz question statistics into its own gem. This patch adds support for Essay question statistics. Closes CNVS-12725 TEST PLAN ---- ---- - create a quiz with an essay question - perform an API request to retrieve the quiz statistics - ensure that the following metrics are generated and correct: - "graded": number of students whose answers have been graded by the teacher - "full_credit": number of students who received a full score - "point_distribution": a list of scores and the number of students who received them (so if 2 students got graded for 3 points, it should have a key of 2 and a value of 3), un-graded submissions should be keyed under null - "responses": number of students who answered the question (wrote anything) - "user_ids": IDs of those students - documentation for QuizStatistics -> Essay should be updated with the new stats > Other things to test - verify that the old statistics page still renders: /courses/:course_id/quizzes/:quiz_id/statistics - verify that you can still generate both student and item analysis CSV reports API endpoint for quiz stats: /api/v1/courses/:courseid/quizzes/:quiz_id/statistics [GET] Change-Id: Ib15434ff4cef89ac211c1f4602d1ee609ef48ec4 Reviewed-on: https://gerrit.instructure.com/33990 Tested-by: Jenkins <jenkins@instructure.com> QA-Review: Caleb Guanzon <cguanzon@instructure.com> Reviewed-by: Derek DeVries <ddevries@instructure.com> Product-Review: Ahmad Amireh <ahmad@instructure.com>
2014-04-20 16:22:49 +08:00
/gems/*/coverage
/gems/*/tmp