2ef7a5191e
Before this fix, there was not a way to determine the workflow_state of the course without accessing API. This fix adds a way to send the course workflow_state during an LTI launch. Test plan: 1) create a course 2) install a tool with the $Canvas.course.workflowState custom field 3) launch the tool and verify that the course workflow_state is passed in the launch parameters Fixes PLAT-1956 Change-Id: I933ddcd45c689ecd054e692c7e4dc993874dc995 Reviewed-on: https://gerrit.instructure.com/94987 Tested-by: Jenkins Reviewed-by: Weston Dransfield <wdransfield@instructure.com> Reviewed-by: Andrew Butterfield <abutterfield@instructure.com> QA-Review: August Thornton <august@instructure.com> Product-Review: Jesse Poulos <jpoulos@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