canvas-lms/gems/lti_outbound
Bracken Mosbacker 5a7cf06508 make the course home lti launch not do content-item
This is a bad default that isn't used by anyone yet, so
remove it as the default action. The ability to do
content item here can be re-added as a configuration
option

Test Plan
 * do a home sub navigation lti launch
 * the content item properties should not be present
   * that is: ext_content_return_url, ext_content_*

Change-Id: I393ccec263481443f7c30a3f2a806a92737937e9
Reviewed-on: https://gerrit.instructure.com/42744
Tested-by: Jenkins
Reviewed-by: Nathan Mills <nathanm@instructure.com>
QA-Review: Clare Strong <clare@instructure.com>
Product-Review: Brad Humphrey <brad@instructure.com>
2015-03-26 19:31:48 +00:00
..
lib make the course home lti launch not do content-item 2015-03-26 19:31:48 +00:00
spec refactor variable substitutions 2015-01-19 21:02:39 +00:00
.rspec rename basic_lti_outbound gem to lti_outbound 2014-01-24 15:48:34 +00:00
Gemfile spec: canvas rspec rake task for vendored_gems 2014-02-24 05:47:34 +00:00
LICENSE.txt rename basic_lti_outbound gem to lti_outbound 2014-01-24 15:48:34 +00:00
README.md rename basic_lti_outbound gem to lti_outbound 2014-01-24 15:48:34 +00:00
Rakefile rename basic_lti_outbound gem to lti_outbound 2014-01-24 15:48:34 +00:00
lti_outbound.gemspec begin rails 4 2014-08-27 23:09:17 +00:00
test.sh bundle check before bundle install for gem tests 2014-06-03 20:09:10 +00:00

README.md

LtiOutbound

TODO: Write a gem description

Installation

Add this line to your application's Gemfile:

gem 'lti_outbound'

And then execute:

$ bundle

Or install it yourself as:

$ gem install lti_outbound

Usage

TODO: Write usage instructions here

Contributing

  1. Fork it ( http://github.com//lti_outbound/fork )
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Add some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create new Pull Request