a3abee9058
This patch updates the LastLocation service to store data from the UI-Router state, rather than the url, which allows us to navigate to a state directly using UI-Router. It also updates the SearchParamProvider to grab its data in the config phase, before the UI-Router is initialized. This permits us to forcefully remove any query parameters passed to our application in the URL - as happens during the OAuth exchange - before the router is aware of them, and thus circumvents an infinite digest loop. The end result is that StoryBoard no longer has to reload itself after a user is successfully authorized. Note: The URL class used is not supported by PhantomJS. As such, PhantomJS has been removed from our karma.conf. Change-Id: Iae113544ad35708f63c5636189f0c88990eab203
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
Grunt tasks
Here are the grunt tasks available with the storyboard-webclient project, the
following commands must be prefixed by grunt, example for the first one, the
command to run will be grunt jshint, the virtualenv must have been
activated see previous section:
jshint: 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.clean: Erases the temporary folders created by various grunt tasks, such as reports, cover and dist.less: Compiles the themes files present in/src/theme/customand/src/theme/customusing less compiler, the result which is a plain css file is stored intodist/styles/main.csscompile: Compiles all of our sources in the dist directory.package: Built code into a release package.build: Compile and packages our code.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 CAUTIONserve: Development server - runs a build and sets up concurrent watchers that will automatically lint, test, and refresh the code when a change is detected.test: Run all the tests.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.jstest:integration: This command will create a clean build against which our integration tests will be run. For more information, please see karma-integration.conf.jstest:functional: This command will create a clean build against which our functional tests will be run. For more information, please see karma-functional.conf.js