32283d03cc
Here I add three major components: Firstly, the API abstractions (resources) that drive our consumption of the storyboard API. Secondly, a series of API mock interceptors that trigger when HTTP requests are made and simulate the existence of the storyboard API. Lastly, a basic UI for project creation, listing, and management. Change-Id: Idbce8252237b0f9fbb9dd2330b952f9a6432c694
23 lines
486 B
JSON
23 lines
486 B
JSON
{
|
|
"name": "storyboard-webclient",
|
|
"version": "0.0.1",
|
|
"dependencies": {
|
|
"jquery": "2.0.3",
|
|
"font-awesome": "4.0",
|
|
"angular": "1.2.9",
|
|
"angular-resource": "1.2.9",
|
|
"angular-cookies": "1.2.9",
|
|
"angular-sanitize": "1.2.9",
|
|
"bootstrap": "3.0.0",
|
|
"angular-ui-router": "0.2.7",
|
|
"angular-translate": "1.1.1"
|
|
},
|
|
"devDependencies": {
|
|
"angular-mocks": "1.2.9",
|
|
"angular-scenario": "1.2.9"
|
|
},
|
|
"resolutions": {
|
|
"angular": "1.2.9"
|
|
}
|
|
}
|