e0c402d42d
Although the project detail view does have an Add story button that does exactly this, it doesn't hurt to set the default project if the dialog is triggered from the header either, since the Add story button is not visible if you scroll down enough, which is probably why this was requested Story: 2001550 Task: 6491 Change-Id: I8cbbdaba4735780d0101df3170de4280a01c214d Signed-off-by: Vaishnavi Pamulapati <vaishnavi.p@research.iiit.ac.in> |
||
---|---|---|
bin | ||
src | ||
test | ||
.eslintignore | ||
.eslintrc | ||
.gitignore | ||
.gitreview | ||
.zuul.yaml | ||
Gruntfile.js | ||
LICENSE | ||
README.md | ||
bindep.txt | ||
karma.conf.js | ||
package.json | ||
protractor-integration.conf.js | ||
protractor.conf.js | ||
tox.ini | ||
yarn.lock |
README.md
StoryBoard Web Client
A WebClient for the OpenStack StoryBoard project.
Project Resources
- Project status, bugs, and blueprints
- Source code
- Documentation
- Additional resources are linked from the project wiki page
- How to contribute to OpenStack
- Code reviews workflow
Getting Started
First of all be sure to have tox installed on your machine then:
- Install the virtualenv containing nodejs:
tox -evenv
- Source the new path containing grunt:
source .tox/venv/bin/activate
- Now you can launch the grunt tasks of storyboard-webclient, by default run
the development server with the following command:
grunt serve
NPM Commands
The following are commands that may be used during project development.
npm run lint
: Runs a linter on the javascript sources files of the project, this will help us keeping style consistency across our files and can reduce the risk of bugs.npm run clean
: Erases the temporary folders created by various grunt tasks, such as reports, cover and dist.npm run build
: Compile and packages our code.npm run serve
: Development server - runs a build and sets up concurrent watchers that will automatically lint, test, and refresh the code when a change is detected.npm run test-unit
: This command will create a clean build against which our unit tests will be run. For more information, please see karma-unit.conf.jsnpm run test-integration
: This command will create a clean build against which our functional tests will be run. For more information, please see protractor-integration.conf.jsnpm run test-functional
: This command will create a clean build against which our functional tests will be run. For more information, please see protractor.conf.js
Grunt tasks
For more detailed development, the following commands are available via grunt.
To run them, you will need to install grunt globally: npm install -g grunt
.
compile
: Compiles all of our sources in the dist directory.package
: Built code into a release package.serve:dist
: This task performs a full build of our application, and then runs that source in a local web server. It does no watching, it simply hosts the files.serve:prod
: This task is identical to 'server:dist', with the exception that it will proxy the API requests against the production API. USE WITH CAUTION