simon/youyesyet
1
0
Fork 0
Code Issues Pull requests Actions Packages Projects Releases Wiki Activity

Documentation changes associated with introdoction of codox

Browse source
This commit is contained in:
simon 2017-07-21 08:46:50 +01:00
parent e77d5d0393
commit c87efe9a66
4 changed files with 11 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
doc/specification/scaling.md
View file

@ -22,7 +22,7 @@ Database reads are probably more infrequent. Each client will obviously need to
Mobile phones typically can have intermittent network access. The client must be able to buffer a queue of records to be stored, and must not prevent the user from moving on to the next doorstep just because the data from the last visit has not yet been stored. There should probably be some on-screen indication of when there is unsent buffered data. Mobile phones typically can have intermittent network access. The client must be able to buffer a queue of records to be stored, and must not prevent the user from moving on to the next doorstep just because the data from the last visit has not yet been stored. There should probably be some on-screen indication of when there is unsent buffered data.
### Pattern of canvassing ### Pattern of canvassing
Canvassing takes place typically between 6:30pm and 9:00pm on a weekday evening. There will be some canvassing outside this period, but not enough to create significant load. Canvassing will be higher on dry nights than on wet ones, and will probably ramp up through the campaign. Canvassing takes place typically between 6:30pm and 9:00pm on a weekday evening. There will be some canvassing outside this period, but not enough to create significant load. Canvassing will be higher on dry nights than on wet ones, and will probably ramp up through the campaign.
@ -40,7 +40,7 @@ This means that the maximum number of transactions per second across Scotland is
700 transactions per second is not a very large number. We should be able to support this level of load on a single server. But what if we can't? 700 transactions per second is not a very large number. We should be able to support this level of load on a single server. But what if we can't?
## Spreading the load ## Spreading the load
### Caching and memoizing ### Caching and memoizing

2
doc/specification/userspec.md
View file

@ -1,4 +1,4 @@
### YouYesYet: User-oriented specification # YouYesYet: User-oriented specification
## Overview ## Overview

7
project.clj
View file

@ -55,12 +55,17 @@
[lein-cljsbuild "1.1.4"] [lein-cljsbuild "1.1.4"]
[lein-uberwar "0.2.0"] [lein-uberwar "0.2.0"]
[lein-bower "0.5.1"] [lein-bower "0.5.1"]
[lein-less "1.7.5"]] [lein-less "1.7.5"]
[lein-codox "0.10.3"]]
:bower-dependencies [[leaflet "0.7.3"]] :bower-dependencies [[leaflet "0.7.3"]]
:cucumber-feature-paths ["test/clj/features"] :cucumber-feature-paths ["test/clj/features"]
:codox {:metadata {:doc "FIXME: write docs"}
:languages [:clojure :clojurescript]
:source-paths ["src/clj" "src/cljc" "src/cljs"]}
:uberwar :uberwar
{:handler youyesyet.handler/app {:handler youyesyet.handler/app
:init youyesyet.handler/init :init youyesyet.handler/init

2
resources/sql/queries.sql
View file

@ -44,6 +44,8 @@ WHERE id = :id
SELECT * FROM addresses SELECT * FROM addresses
WHERE id = :id WHERE id = :id
-- :name get-addresses-by-postcode
-- :name delete-address! :! :n -- :name delete-address! :! :n
-- :doc delete a address given the id -- :doc delete a address given the id
DELETE FROM addresses DELETE FROM addresses