| Commit message (Collapse) | Author | Age | Lines |
|---|
| |
|
|
|
|
| |
If a user had no confirmed updates, but did have e.g. an unconfirmed
update that had mark_fixed set, you would get an error when trying to
hide the user's reports/updates.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
After this change, you can safely add the TfL body to other councils
(namely the ones surrounding London that include TfL bus stops);
clicking in those councils on other cobrands will have no change, as the
TfL body will be fully ignored on a non-London council, but on the TfL
cobrand it will allow it for e.g. the selection of bus stops outside
London.
It removes the body rather than just all its categories to prevent a "We
do not have details of the other body covering this area" message
appearing.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This fixes a bug where the new tree plantings group was requiring a tree
group to be selected, which isn't the desired behaviour.
The bug was caused by the group layer not having the same `relevant`
function as the points layers. This adds the shared bits into a shared
config that the assets both use.
Also hide the asset item message for request to plant a new tree
category.
|
| |
|
|
|
| |
We always want a tree code for tree reports, so add the code needed to
make the asset selection step mandatory.
|
| |
|
|
|
|
| |
Checks that the correct bits of the problem's extra fields are sent when
creating the report in Open311, and that extra bits of info are sent
when sending comments to Open311.
|
| |
|
|
|
|
|
|
| |
This allows you to restrict the message to a certain group of
categories.
This is so we can add a "is this problem on private land" message to the
categories in the "Trees" group for Peterborough.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We don't want to plant trees where there are already trees, so we add a
separate layer for new tree requests, and disable pin snapping for that
layer.
This adds a new option for layers named "relevant". If provided it will
be called with an options object, allowing you to check ".category" and
".group" and return a boolean for whether you want to display the layer
based on the passed options.
Note: You still need to provide an "asset_group" option even if you use
the "relevant" option as this is used elsewhere.
The "regular" tree-points layer uses this to exclude just the new trees
subcategory from being displayed.
|
| |
|
|
| |
Two layers, one for tree points, the other for tree groups.
|
| |
|
|
|
|
| |
This field is shown in the FMS interface, but doesn't need to be sent to
open311, it's just to check that the user isn't reporting problems on
private land.
|
| |
|
|
|
| |
This is needed to route reports correctly when using the "Multi"
backend.
|
| |
|
|
|
| |
We need the FMS ID so we can send it through to ezytreev, as that
matches updates to existing reports using the FMS ID.
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| | |
Rather than setting a min_resolution on all of the cobrands just set a
default in web/cobrands/fixmystreet/assets.js. This means that assets
will appear at all zoom levels, which seems like what we want to happen
most of the time.
|
| | | |
|
| |\ \ |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
If a line asset spans two tiles it seems like it's included in both
tiles which means you end up with it added to a layer twice. This means
you get two overlaid identical assets which, when combined with low
opacity colours produces inconsistent colours. This uses the `fid` to
check for duplicates on adding.
|
| | | |
| | |
| | |
| | |
| | | |
If the options to either road or asset layer include a `class` attribute
then use the Layer class there, otherwise the defaults.
|
| | | |
| | |
| | |
| | | |
All servers connected to are using 39.37.
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Hard code the resolution as it only ever used the one value which isn't
the same in the 27700 based map. This is to avoid pulling in asset
groups.
|
| | | |
| | |
| | |
| | | |
Use Northamptonshire map tiles via WMS.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
Basic config and setup files for using WMS based map tiles. These still
require config in appropriate cobrand perl and javascript files
|
| | | |
| | |
| | |
| | | |
Non-JS clicking does not work if map tiles are scaled.
|
| |/ /
| |
| |
| |
| |
| | |
We already had these but labeled as EPSG:900913 which is the same as
3857. However, we tend to use 3857 as not all map servers recognise
900913.
|
| | | |
|
| | |
| |
| |
| | |
Easier working with CSP headers.
|
| | | |
|
| |/ |
|
| |\ |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This basic service worker behaves identically to the existing appcache -
some static scripts and CSS are cached, any HTML offline instead returns
a static HTML page that knows how to show data on stored problems out of
localStorage (stored there when /my/planned was visited online). Inspect
form submissions will be captured and can be synced back when online.
Once feature parity is established, we will then remove appcache, switch
from using localStorage to the cache API, and hopefully move all offline
support into the service worker.
|
| | |
| |
| |
| |
| | |
Reads information from a theme object if present, and icons from a
theme directory, with fallbacks.
|
| | | |
|
| |/
|
|
| |
Not caught by test because App is loaded in tests.
|
| |\ |
|
| | | |
|
| | | |
|
| | | |
|
