Added basic styling and messages to 404 and 500 pages
Hide the edit link for completed services
Don't show a page of questions for a completed listing
Prevent completed service from being saved
Listing objects not building properly for integration tests - work around in controller
Warn user if eSourcing ID has not been provided

If a user has not entered their eSourcing account ID in the
Digital Marketplace then we should warn them while they are
submitting their services.

This is because their services cannot be published on the
Digital Marketplace if we do not have this information to
reconcile the two systems.

The eSourcing account ID gets passed across in the cookie.
It will either be 9 numbers or not specified. If it is not
specified then the view will receive an empty string.

*So while I cannot test locally that this actually works
I am fairly confident that it will*
Fix the delete functionality

- Showing the delete message replicates some of the functionality
  of the method for rendering a summary page
- The way that data is passed from the summary page method to
  the view has changed
- The delete method has now been updated to reflect this
Merge pull request #124 from alphagov/fix-delete-functionality

Fix the delete functionality
Remove unused imports from home page
Prevent edit of completed before validation

- It makes more sense to prevent the editing of a completed service
  before any validation happens—whether or not the response
  validates is moot because it will never be saved
- It's also a slightly cleaner solution because it means not
  wrapping all of the saving functionality in a conditional
Merge pull request #121 from alphagov/completed-not-editable

Ensure that completed services can't be edited
Merge pull request #123 from alphagov/show-esourcing-warning

Warn user if eSourcing ID has not been provided
Updated error page views to mirror DM
Added SaSS files to style error pages
Tidy up naming of classes in SASS
Display saved values on page 16

Previously saved values were not repopulating on page 16. This fixes the issue.
Merge pull request #119 from alphagov/error_pages

Added basic styling and messages to 404 and 500 pages
Merge pull request #130 from alphagov/page_16_data_save

Display saved values on page 16
Display all error messages on all pages

Custom error messages were not being shown on all pages.

This introduces a new method on the Fixtures class that retrieves an
error message. It first checks if the message is a key in the
content.properties file. If not, it returns the message as is. This
allows custom messages to be defined in the controller where necesarry.
This was already being done but they weren't being displayed in the
frontend.

On questions with multiple text values (eg. features and benefits), only
one error is shown per question rather than one per question value.
Because of this the validation message has to be keyed by the question
key rather than the value key.
Update content to include latest changes