5a7cf06508
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> |
||
---|---|---|
.. | ||
lib | ||
spec | ||
.rspec | ||
Gemfile | ||
LICENSE.txt | ||
README.md | ||
Rakefile | ||
lti_outbound.gemspec | ||
test.sh |
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
- Fork it ( http://github.com//lti_outbound/fork )
- Create your feature branch (
git checkout -b my-new-feature
) - Commit your changes (
git commit -am 'Add some feature'
) - Push to the branch (
git push origin my-new-feature
) - Create new Pull Request