CSC/ECE 517 Fall 2013/oss ans: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 7: | Line 7: | ||
* Reduce the method complexity in the response controller | * Reduce the method complexity in the response controller | ||
* Remove duplicated code | * Remove duplicated code | ||
* There were “custom_create” and “custom_update” methods for “custom” (multipart) rubrics. We already had create and update methods that were handling the normal rubrics. Our job was to use polymorphism in order to eliminate the custom methods | * There were “custom_create” and “custom_update” methods for “custom” (multipart) rubrics. We already had create and update methods that were handling the normal rubrics. Our job was to use polymorphism in order to eliminate the custom methods. | ||
== Design Choices == | |||
=== Refactoring carried out === | |||
==Future Work == | ==Future Work == | ||
== Appendix == | == Appendix == | ||
Revision as of 03:00, 30 October 2013
E807 : Refactoring and testing response_controller.rb
Introduction
The response controller creates, edits, and displays responses, that is, rubrics to be filled out, or filled-out rubrics. Our project requirement entailed the following things to be done.
- Reduce the method complexity in the response controller
- Remove duplicated code
- There were “custom_create” and “custom_update” methods for “custom” (multipart) rubrics. We already had create and update methods that were handling the normal rubrics. Our job was to use polymorphism in order to eliminate the custom methods.