app/main/__init__.py

from flask import Blueprint

main = Blueprint('main', __name__)
no_cookie = Blueprint('no_cookie', __name__)

from app.main.views import (  # noqa isort:skip
    add_service,
    agreement,
    api_keys,
    broadcast,
    choose_account,
    code_not_received,
    conversation,
    dashboard,
    email_branding,
    feedback,
    find_services,
    find_users,
    forgot_password,
    history,
    inbound_number,
    index,
    invites,
    jobs,
    letter_branding,
    manage_users,
    new_password,
    notifications,
    organisations,
    platform_admin,
    providers,
    register,
    returned_letters,
    send,
    service_settings,
    sign_in,
    sign_out,
    templates,
    two_factor,
    tour,
    uploads,
    user_profile,
    verify,
)
Start to create views 2015-11-20 16:22:44 +00:00			`from flask import Blueprint`

Fix isort breaking things 2019-03-25 10:47:00 +00:00			`main = Blueprint('main', __name__)`
add no_cookie blueprint we have a hunch that some session related issues that we've seen over the last few weeks might be related to weird race conditions where cookies set by subresources (image previews of letters on the send flow) arrive just as the img request is cancelled because the user has clicked on a button to navigate to a new page, but still manage to set the cookie? We're not entirely sure what's going on, but we've got a hunch that not setting cookies on image fetches sounds sensible. Images are always loaded as a subresource (ie: through a `src` tag in an html element), so they should never need to change the cookies, so this seems sensible. We've done this by creating a new blueprint that doesn't set session.permanent, and doesn't call `save_serivce_or_org_after_request` either. cookies are sent back to the browser if: `sesion.modified or (session.permanent and 'REFRESH_EVERY_REQUEST')` (where the latter is a config setting). Turning off REFRESH_EVERY_REQUEST (which is True by default) means that we will only update the sesion if it's been modified. In practice, literally every request is modified in the after_request handler `save_service_or_org_after_request`. This is accidentally convenient, as it guarantees that we'll still send back the cookie normally even though refresh_every_request is disabled. Sending back the cookie updates the expiry time (20 hours), so we need to keep doing this to preserve existing session timeout behaviour. 2019-11-28 14:39:30 +00:00			`no_cookie = Blueprint('no_cookie', __name__)`
Fix isort breaking things 2019-03-25 10:47:00 +00:00
			`from app.main.views import ( # noqa isort:skip`
[WIP] Start of user accepting invite. This commit only deals with acceptance by users who are already in system. Changed invite client to return invited user objects instead of dictionaries. Added commented out test. fixed up fixtures to return invited user object for invites 2016-02-29 17:35:21 +00:00			`add_service,`
Run isort 2019-03-25 10:25:05 +00:00			`agreement,`
			`api_keys,`
Add some views for selecting broadcast areas These are just so we have some pages to click through for now. They don’t use real templates, or any of the broadcast stuff from the database. But I think it’s useful to get some skeleton pages in first so that we can see the map etc working in production, then build on that, without having to do it all in one mega PR. For that reason there are two short term things I’ve done in this commit which should be revisited soon: - no tests for the endpoints - data about which areas are selected is stored in the session 2020-07-06 10:53:14 +01:00			`broadcast,`
Run isort 2019-03-25 10:25:05 +00:00			`choose_account,`
[WIP] Start of user accepting invite. This commit only deals with acceptance by users who are already in system. Changed invite client to return invited user objects instead of dictionaries. Added commented out test. fixed up fixtures to return invited user object for invites 2016-02-29 17:35:21 +00:00			`code_not_received,`
Run isort 2019-03-25 10:25:05 +00:00			`conversation,`
New platform-admin-dashboard page 2016-05-24 15:52:44 +01:00			`dashboard,`
Run isort 2019-03-25 10:25:05 +00:00			`email_branding,`
Added provider management pages in. - see priority - change priority 2016-05-11 09:43:55 +01:00			`feedback,`
Find services by name or partial name 2019-08-13 16:25:26 +01:00			`find_services,`
find_users_by_email view loads a page with search form and is linked to 2018-07-06 11:10:14 +01:00			`find_users,`
Run isort 2019-03-25 10:25:05 +00:00			`forgot_password,`
Move service history into it own file We’re going to do some work on this page, let’s put it in a sensible place first before we add a bunch more code to the wrong place. 2019-10-18 09:18:51 +01:00			`history,`
Run isort 2019-03-25 10:25:05 +00:00			`inbound_number,`
			`index,`
			`invites,`
			`jobs,`
Add page to create new letter branding This has a form with 3 fields - the file upload field, logo name, and an optional logo domain. Logos need to be uploaded in `.svg` format and we then convert this to `.png` format and upload both file types to S3 as well as saving the letter branding details in the database. 2019-01-31 16:56:35 +00:00			`letter_branding,`
Run isort 2019-03-25 10:25:05 +00:00			`manage_users,`
			`new_password,`
Inbound number admin page 2017-08-08 10:24:54 +01:00			`notifications,`
Run isort 2019-03-25 10:25:05 +00:00			`organisations,`
			`platform_admin,`
			`providers,`
			`register,`
New pages to show a summary of all the reports the services has for its returned letters 2019-12-17 17:23:00 +00:00			`returned_letters,`
Run isort 2019-03-25 10:25:05 +00:00			`send,`
			`service_settings,`
			`sign_in,`
			`sign_out,`
			`templates,`
			`two_factor,`
Add view for new tour start page This will replace the current tour start page 2020-09-29 14:48:56 +01:00			`tour,`
Add 'Uploads' hub and navigation The uploads hub is just a page with text for now - there are no actions available on the page. It is linked to from a new 'Uploads' menu item on the left of the page which is only visible if your service has the `letter` and `upload_letters` permissions and if the current user has permissions to send messages. 2019-08-09 08:44:11 +01:00			`uploads,`
Run isort 2019-03-25 10:25:05 +00:00			`user_profile,`
			`verify,`
Make data consistent from dashboard -> job - adds a table of recent activity to the job page, which is shared by the dashboard page - uses the same filename and message template as the first job shown on the dashboard - sets the time of file uploads/message delivery/message sending to always match ‘just now’ 2015-12-18 10:26:56 +00:00			`)`