context split into get_context_response and get_context
delete_context split into delete_context_response and delete_context
create_context split into create_context_response and create_context
specifications split into get_specifications_response and get_specifications
delete_specifications split into delete_specifications_response and delete_specifications
create_specifications split into create_specifications_response and create_specifications
The "response" methods are accessible through an API url, while the "non-response" methods are purely server-side
The purely server-side "non-response" methods allow you to modify the @context and specifications of packages without having to make calls from the front-end
Useful for strictly server-side operations
The "response" methods functions call the "non-response" methods, have the same API urls as the previous "non-split" methods, and therefore provide the same functionality as the "non-split" methods before
New chain of events when adding cart items
geem_cart.init_cart_tab calls new method geem_api.GeemAPI.get_cart_items
geem_api.GeemAPI.get_cart_items calls new method views.ResourceViewSet.add_cart_items_to_package
views.ResourceViewSet.add_cart_items_to_package calls several methods for each cart item to add it to the target package
An object detailing the result of each attempted cart item addition makes its way back to geem_cart.init_cart_tab, which reports any failures
@ddooley I removed code that was responsible for the old way of doing things in commit 1dadcde
Please review this commit, and tell me if you are okay with getting rid of this code, or if you want to keep this code around for the future--in which case I can revert the commit
Small changes
Added a damion_packages.json fixture, which provides a useful set of packages to work with during the development stage
Removed 127.0.0.1 mapping of db port
Makes debugging of database difficult when using docker-machine
Split several views into multiple functions
Splits
context
split intoget_context_response
andget_context
delete_context
split intodelete_context_response
anddelete_context
create_context
split intocreate_context_response
andcreate_context
specifications
split intoget_specifications_response
andget_specifications
delete_specifications
split intodelete_specifications_response
anddelete_specifications
create_specifications
split intocreate_specifications_response
andcreate_specifications
The "response" methods are accessible through an API url, while the "non-response" methods are purely server-side
The purely server-side "non-response" methods allow you to modify the
@context
andspecifications
of packages without having to make calls from the front-endUseful for strictly server-side operations
The "response" methods functions call the "non-response" methods, have the same API urls as the previous "non-split" methods, and therefore provide the same functionality as the "non-split" methods before
New chain of events when adding cart items
geem_cart.init_cart_tab
calls new methodgeem_api.GeemAPI.get_cart_items
geem_api.GeemAPI.get_cart_items
calls new methodviews.ResourceViewSet.add_cart_items_to_package
views.ResourceViewSet.add_cart_items_to_package
calls several methods for each cart item to add it to the target packageAn object detailing the result of each attempted cart item addition makes its way back to
geem_cart.init_cart_tab
, which reports any failures@ddooley I removed code that was responsible for the old way of doing things in commit 1dadcde
Small changes
Added a
damion_packages.json
fixture, which provides a useful set of packages to work with during the development stageRemoved
127.0.0.1
mapping ofdb
port