We are having problems in some files, that don't have cr at the end
of the file. Some other editors are automatically adding it, so it's
highlighting non-existent differences on gerrit when editing.
Add grunt-lintspaces to ensure that all js files end with newline.
Update all the files to end with a CR to prevent these errors.
Change-Id: If0c89399dbb5cdf94384e979a3cfe8038850193b
Story: 2000089
This adds a config.json file configured so that any docs-draft build
will be able to consume the api at storyboard.openstack.org. For more
information, see https://review.openstack.org/#/c/124211/
This patch won't actually do anything until the js-draft build
has been taught to upload this file.
Change-Id: I03a5be78e6188b51f7221fe782f6a7792b55a79f
With the ability to customize the application using config.json, the
complex config discovery used for storyboardApiBase is no longer
necessary. This removes it.
Change-Id: Ie6d0390e30c24b2ca22bd389a817c40823ab80b1
An effort to abstract query parameters so that the resources inform
the system itself how the API is exposed. Could be the first step in
making our API self-describing.
- Deprecated Browse, it was serving only as an abstraction layer
for Criteria.
- The Criteria service now provides several lambda builders to assist
in the generation of search criteria. Filtering criteria against a
resource, mapping criteria against parameters, and generating search
lambdas.
- Search Criteria controller now has an initialization method that
allows you to configure it at runtime to the resource it's supposed to
provide search criteria for.
- Criteria Tag Item has been split out to be more generic.
- Managing criteria has been delegated to the resource itself. Now
it falls to Project, Story, etc. to inform the system what fields
it accepts as query parameters.
- Common text criteria resolver has been added.
- Header controller has been switched to use new Resource Criteria API.
- Stories may now be queried on the Story Status field.
- Services are now generated via a service factory rather than by
using storyboardApiSignature.
- Search is now handled via the resource.search() method.
Change-Id: I1e355320c90f7cdc8cb6ee2191fe819ff7094665
This patch adds the notification module, a mostly-self contained way
of surfacing errors, warnings and notifications to the user. These
can either be initiated by the application, or can be received from
the server. Among other things, the impact of this will be that
the user will be notified if one of our HTTP requests fails. This
fixes the situation where storyboard would 'fail silently' when
someone is trying to accomplish something.
- New notification module.
- Notifications directive, for a list of all notifications that
made it past filters.
- New Notification service that handles all error broadcasts in the
system.
- New severity directive.
- HTTP Error broadcaster now uses the notification service.
- Session now uses Notification service to handle 401 errors.
- Added new notification filters to strip out 200's and template load
requests.
Change-Id: I4aaa50404560d1c1f14f639e3ac68b2ac2d4380c
Tests are good. These put some sane rules around our random string
generation utilities, and provides demo code for writing convenience
test methods that can be applied to the global testing environment.
Change-Id: Ib03382068bf3165addc4d96595850b6b0c3087cb
The Async spec in jasmine was updated, and includes the ability to
register custom matchers. I've upgraded our unit tests to make use
of this new framework.
Change-Id: Id00d29df7e0b41f01f5fe68e1b1d86a224e9505b
- Created StringUtil class with some useful random string methods.
- Create UrlUtil class with useful URL manipulation and builder methods.
- Cleaned up some unused libraries (cookies, mocks) from index.html
- Added LocalStorage dependency.
- Added advanced routing to auth module for OAuth response routing.
- Added state resolver methods so we can enforce UI states that require
certain session states.
- Removed AuthProvider resolver and resource, as they're no longer necessary.
- Updated header to point to correct routes.
- Updated header to correctly represent state.
- Added busy template for "pending" activity. This shouldn't actually show up
because the javascript will resolve the view logic too quickly, but it's
included for the sake of completion.
- Added error state in case we get an error response from the server. It's
very basic.
- Added request interceptor that attaches an access token to every request
if a valid access token exists.
- Added OpenId service to handle our redirection and token resolution.
- Added Deauthorization (logout) controller.
- Added session management controller.
- Added search param provider to inject non-hashbang query parameters.
Change-Id: Id9b1e7fe9ed98ad4be0a80f1acd4a9e125ec57c9
This patch includes two fixes. First, it disables our functional tests
because of a bug in grunt-connect-proxy, which is fixed by an
as-yet-not-accepted patch here:
81631b20c5
Secondly, it includes a temporary fix for the recent NPM CA chain update
explained here:
http://blog.npmjs.org/post/78085451721/npms-self-signed-certificate-is-no-more
The basic premise is that the node package manager no longer supports
their self-signed certificate. This is good! Unfortunately, the
released version of npm is 1.4.4, but the one packaged with nodejs
0.10.26(stable) is 1.4.3. Until nodejs updates itself, we need to
temporarily bork the ca chain to update npm.
Since we're using throwaway slaves, and it's a temporary fix, and
node is only used for builds, I feel this is an acceptable risk.
Change-Id: Ic510e55355966591affbe25ce3f831ca424b2afa
This patch constitutes the work discussed in Brussels for the MVP webclient.
Changes made, as follows:
1- Updated header to contain Overview, Projects, Stories, and a "New Story"
button, including mobile treatment.
2- Updated navigation header to use selection styling for mobile and regular.
3- Application index contains new-story button.
4- Main application container now has a minheight.
5- Removed old controllers (code cleanup) before reimplementation.
6- Wired project views (require API support).
7- Wired story views (require API support).
8- Wired new story modal (require API support).
9- New task form (requires API support).
10- Wired up new functional tests and fixed a few issues in existing unit
tests.
11- Switched LESS compiler from recess to less, since recess can no longer
compile the most recent version of bootstrap.
Change-Id: Iddd5b29dd899d92f05ad7a9a63814d8599e167d4
Turns out the wsgi module on the hosted storyboard api has a root path of /api/v1,
rather than /v1 as in the dev environment. This change fixes the default in the
webclient. The API's changes will be done independently.
Change-Id: I3242df5886db96509561db81ef5b082bed3264da
This commit makes use of previous API inclusions and resource frameworks to
demonstrate a simple list round-trip from server to client. To properly see
it in action, please retrieve CR 68540 and run that alongside grunt server.
It will allow you to create, edit, and list project groups with a simple UI.
Change-Id: Ie95685a6fd3cd3ab2b674bef3685b2896eb72f0d
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
Two new functional tests that assert that when a user attempts to access
any route in the /auth statechart, it will resolve to the list.
Change-Id: I28655c513aacf49b8f7a398f99929ddfcf61c372
This contains the initial commit for the storyboard web client
project, consisting of the basic build & testing harnesses,
simple set of routes, and a list of basic dependencies
necessary to run an application. It's purpose is to be
reference Javascript/Angular project to test out the build
images.
Adam Coldrick