Rename Day8 to day8 in GitHub URL

Author: superstructor

CHANGES.md

@@ -14,8 +14,8 @@ y'know. Pretty good.
 
 
 [![Clojars Project](https://img.shields.io/clojars/v/re-frame.svg)](https://clojars.org/re-frame)
-[![GitHub license](https://img.shields.io/github/license/Day8/re-frame.svg)](license.txt)
-[![Circle CI](https://circleci.com/gh/Day8/re-frame/tree/master.svg?style=shield&circle-token=:circle-ci-badge-token)](https://circleci.com/gh/Day8/re-frame/tree/master)
+[![GitHub license](https://img.shields.io/github/license/day8/re-frame.svg)](license.txt)
+[![Circle CI](https://circleci.com/gh/day8/re-frame/tree/master.svg?style=shield&circle-token=:circle-ci-badge-token)](https://circleci.com/gh/day8/re-frame/tree/master)
 
 ## re-frame
 
@@ -531,14 +531,14 @@ At this point, you know 50% of re-frame.  <br>
 The full [docs are here](/docs/README.md) and the [FAQs are here](/docs/FAQs/README.md).
 
 There are two example apps to play with: <br>
-https://github.com/Day8/re-frame/tree/master/examples
+https://github.com/day8/re-frame/tree/master/examples
 
 Use a template to create your own project: <br>
-Client only:  https://github.com/Day8/re-frame-template  <br>
+Client only:  https://github.com/day8/re-frame-template  <br>
 Full Stack: http://www.luminusweb.net/
 
 And please be sure to review these further resources: <br>
-https://github.com/Day8/re-frame/blob/master/docs/External-Resources.md
+https://github.com/day8/re-frame/blob/master/docs/External-Resources.md
 
 ### T-Shirt Unlocked
 

README.md

@@ -16,9 +16,9 @@ src
 └── subs.cljs         <--- subscription handlers  (query layer)
 ```
 
-For a living example of this approach, look at the [todomvc example](https://github.com/Day8/re-frame/tree/master/examples/todomvc).
+For a living example of this approach, look at the [todomvc example](https://github.com/day8/re-frame/tree/master/examples/todomvc).
 
-*No really, you should absolutely look at the [todomvc example](https://github.com/Day8/re-frame/tree/master/examples/todomvc) example, as soon as possible. It contains all sorts of tips.*
+*No really, you should absolutely look at the [todomvc example](https://github.com/day8/re-frame/tree/master/examples/todomvc) example, as soon as possible. It contains all sorts of tips.*
 
 ### There's A Small Gotcha
 
@@ -98,7 +98,7 @@ Where the first option might be preferrable since it ensures you require the han
 ## I Want Real Examples!
 
 Maybe look here: 
-https://github.com/Day8/re-frame/blob/master/docs/External-Resources.md#examples-and-applications-using-re-frame
+https://github.com/day8/re-frame/blob/master/docs/External-Resources.md#examples-and-applications-using-re-frame
 
 ***
 

docs/App-Structure.md

@@ -74,7 +74,7 @@ And this enables us to catch errors early (and accurately). It increases confide
 that Types can increase confidence, only [a good schema can potentially provide more
 **leverage** than types](https://www.youtube.com/watch?v=nqY4nUMfus8).
 
-4. Undo/Redo [becomes straight forward to implement](https://github.com/Day8/re-frame-undo).
+4. Undo/Redo [becomes straight forward to implement](https://github.com/day8/re-frame-undo).
 It is easy to snapshot and restore one central value. Immutable data structures have a
 feature called `structural sharing` which means it doesn't cost much RAM to keep the last, say, 200
 snapshots. All very efficient.
@@ -99,7 +99,7 @@ Of course, that means you'll have to learn [spec](http://clojure.org/about/spec)
 some overhead in that, so maybe, just maybe, in your initial experiments, you can
 get away without one. But not for long.  Promise me you'll write a `spec`.  Promise me.  Okay, good.
 
-Soon we'll look at the [todomvc example](https://github.com/Day8/re-frame/tree/master/examples/todomvc)
+Soon we'll look at the [todomvc example](https://github.com/day8/re-frame/tree/master/examples/todomvc)
 which shows how to use a spec.  (Check out `src/db.cljs` for the spec itself, and then in `src/events.cljs` for
 how to write code which checks `app-db` against this spec after every single event has been
 processed.)

docs/ApplicationState.md

@@ -10,8 +10,8 @@ In this tutorial, **we look at re-frame code**. By the end of it, you'll be at 7
 
 ## What Code?
 
-This repo contains an `/examples` application called ["simple"](https://github.com/Day8/re-frame/tree/master/examples/simple),
-which contains 70 lines of code. We'll look at every line of [the file](https://github.com/Day8/re-frame/blob/master/examples/simple/src/simple/core.cljs).
+This repo contains an `/examples` application called ["simple"](https://github.com/day8/re-frame/tree/master/examples/simple),
+which contains 70 lines of code. We'll look at every line of [the file](https://github.com/day8/re-frame/blob/master/examples/simple/src/simple/core.cljs).
 
 This app:
  - displays the current time in a nice big, colourful font
@@ -27,7 +27,7 @@ To run the code yourself:
  * Install leiningen  (http://leiningen.org/#install)
 
 Then:
-  1. `git clone https://github.com/Day8/re-frame.git`
+  1. `git clone https://github.com/day8/re-frame.git`
   2. `cd re-frame/examples/simple`
   3. `lein do clean, figwheel`
   4. wait a minute and then open <http://localhost:3449/example.html>
@@ -45,7 +45,7 @@ An online, interactive version of this tutorial page is [available here](http://
 ## Namespace
 
 Because this example is tiny, the source code is in a single namespace:
-https://github.com/Day8/re-frame/blob/master/examples/simple/src/simple/core.cljs
+https://github.com/day8/re-frame/blob/master/examples/simple/src/simple/core.cljs
 
 Within this namespace, we'll need access to both `reagent` and `re-frame`. 
 So, at the top, we start like this: 
@@ -327,7 +327,7 @@ Here's the code:
 ```
 
 Like I said, both of these queries are trivial. 
-See [todomvc.subs.clj](https://github.com/Day8/re-frame/blob/master/examples/todomvc/src/todomvc/subs.cljs) 
+See [todomvc.subs.clj](https://github.com/day8/re-frame/blob/master/examples/todomvc/src/todomvc/subs.cljs) 
 for more interesting ones.
 
 ## View Functions (domino 5)
@@ -492,13 +492,13 @@ structure exists in `app-db` before any subscriptions or event handlers run.
 ## Next Steps
 
 You should now take time to carefully review the 
-[todomvc example application](https://github.com/Day8/re-frame/tree/master/examples/todomvc).
+[todomvc example application](https://github.com/day8/re-frame/tree/master/examples/todomvc).
 On the one hand, it contains a lot of very helpful practical advice. On the other, it does
 use some more advanced features like `interceptors` which are covered later in the docs.   
 
 After that, you'll be ready to write your own code.  Perhaps you will use a
 template to create your own project: <br>
-Client only:  https://github.com/Day8/re-frame-template  <br>
+Client only:  https://github.com/day8/re-frame-template  <br>
 Full Stack: http://www.luminusweb.net/
 
 Obviously, you should also go on to read the further documentation.

docs/CodeWalkthrough.md

@@ -1,5 +1,5 @@
 >  The methods described in this page are now out of date. Included for historical reasons only.  
-> [re-frame-10x](https://github.com/Day8/re-frame-10x) is now our recommeded tool. 
+> [re-frame-10x](https://github.com/day8/re-frame-10x) is now our recommeded tool. 
 
 ---
 
@@ -88,7 +88,7 @@ Then the customised tracer for cljs-devtools that includes a colour choice
 [![Clojars Project](http://clojars.org/day8/re-frame-tracer/latest-version.svg)](http://clojars.org/day8/re-frame-tracer)
 
 
-Next, we're going to assume that you have structured you app in the [recommended way](https://github.com/Day8/re-frame/tree/master/examples/todomvc/src/todomvc),
+Next, we're going to assume that you have structured you app in the [recommended way](https://github.com/day8/re-frame/tree/master/examples/todomvc/src/todomvc),
 meaning you have the namespaces `events.cljs`, `subs.cljs` and `views.cljs`.
 It is the functions within these namespaces that we wish to trace.  
 
@@ -207,7 +207,7 @@ If you are using v0.8.0 or later, then you can ignore this section.
 Prior to v0.8.0, subscriptions were done using `re-frame.core/reg-sub-raw`, 
 instead of `re-frame.core/reg-sub` (which is now the preferred method). 
 
-Details of the changes can [be found here](https://github.com/Day8/re-frame/blob/master/CHANGES.md#080--20160819).
+Details of the changes can [be found here](https://github.com/day8/re-frame/blob/master/CHANGES.md#080--20160819).
 
 When using `re-frame.core/reg-sub-raw`, you must explicitly use `reaction`.  And 
 unfortunately both `trace-forms` and `reaction` are macros and they don't work well together.

docs/Debugging.md

@@ -41,12 +41,12 @@ This EP proposes that:
 ## Motivations
 
 There's pressure from multiple directions to collect and retain more metadata about handlers: 
-  - tickets like [#457](https://github.com/Day8/re-frame/issues/457) want docstrings for handlers
+  - tickets like [#457](https://github.com/day8/re-frame/issues/457) want docstrings for handlers
   - adding specs for events, so they can be checked at dev time
   - when re-frame becomes less of a framework and more of a library, handlers might 
     need be "grouped" into "packages". So "package" information about handlers need to be supplied and retained.
   - Tooling support - we'd like `re-frame-10x` to actively help programmers when they are learning a 
-    new code base. That's one of [the four stated goals](https://github.com/Day8/re-frame-10x#helps-me-how). 
+    new code base. That's one of [the four stated goals](https://github.com/day8/re-frame-10x#helps-me-how). 
     Ideally, re-frame would be capable of providing tooling with "a complete 
     inventory" of an app's handlers, along with useful
     metadata on each handles. When an event is processed, the audit trail of 

docs/EPs/001-CaptureHandlerMetadata.md

@@ -63,7 +63,7 @@ progressive mutation of a global `registrar` (map) held internally within `re-fr
 Each registration adds a new entry to this `registrar`. 
 
 If you are troubled by the thought of side effects on globals, there's 
-an [FAQ entry you may find interesting](https://github.com/Day8/re-frame/blob/master/docs/FAQs/ViewsOnGlobalRegistration.md).
+an [FAQ entry you may find interesting](https://github.com/day8/re-frame/blob/master/docs/FAQs/ViewsOnGlobalRegistration.md).
 
 ### Problem 1:  Frames And Registrars
 

docs/EPs/002-ReframeInstances.md

@@ -9,7 +9,7 @@ Please add to this list by submitting a pull request.
 
 ### Templates
 
-* [re-frame-template](https://github.com/Day8/re-frame-template) - Generates the client side SPA
+* [re-frame-template](https://github.com/day8/re-frame-template) - Generates the client side SPA
 * [Luminus](http://www.luminusweb.net) - Generates SPA plus server side.
 * [re-natal](https://github.com/drapanjanas/re-natal) - React Native apps.
 * [Slush-reframe](https://github.com/kristianmandrup/slush-reframe) - A scaffolding generator for re-frame run using NodeJS. Based on re-frame `0.7.0`
@@ -18,7 +18,7 @@ Please add to this list by submitting a pull request.
 
 ### Examples and Applications Using re-frame
 
-* [RealWorld](https://github.com/jacekschae/conduit) - heavily inspired by [todomvc](https://github.com/Day8/re-frame/tree/master/examples/todomvc) - well commented codebase with CRUD, auth, advanced patterns, etc) that adheres to the [RealWorld](https://github.com/gothinkster/realworld) spec and API.
+* [RealWorld](https://github.com/jacekschae/conduit) - heavily inspired by [todomvc](https://github.com/day8/re-frame/tree/master/examples/todomvc) - well commented codebase with CRUD, auth, advanced patterns, etc) that adheres to the [RealWorld](https://github.com/gothinkster/realworld) spec and API.
 * [BlueGenes](https://github.com/intermine/bluegenes) - searching and analysing genomic data, by the University of Cambridge
 * [Memento](https://gitlab.com/Numergent/memento) a private note-taking app. Uses compojure-api, PostgreSQL and token auth.
 * [RealWord](https://github.com/polymeris/re-frame-realword-example-app) has CRUD, auth. Adheres to [RealWorld](https://github.com/gothinkster/realworld) spec and API.
@@ -42,9 +42,9 @@ Please add to this list by submitting a pull request.
 
 ### Effect and CoEffect Handlers
 
-* [async-flow-fx](https://github.com/Day8/re-frame-async-flow-fx) - manage a boot process dominated by async
-* [http-fx](https://github.com/Day8/re-frame-http-fx) - performing Ajax tasks (via cljs-ajax)
-* [re-frame-forward-events-fx](https://github.com/Day8/re-frame-forward-events-fx) - slightly exotic
+* [async-flow-fx](https://github.com/day8/re-frame-async-flow-fx) - manage a boot process dominated by async
+* [http-fx](https://github.com/day8/re-frame-http-fx) - performing Ajax tasks (via cljs-ajax)
+* [re-frame-forward-events-fx](https://github.com/day8/re-frame-forward-events-fx) - slightly exotic
 * [cookie-fx](https://github.com/SMX-LTD/re-frame-cookie-fx) - set and get cookies
 * [document-fx](https://github.com/SMX-LTD/re-frame-document-fx) - set and get on `js/document` attributes
 * [re-frame-youtube-fx](https://github.com/micmarsh/re-frame-youtube-fx) - YouTube iframe API wrapper
@@ -68,8 +68,8 @@ Please add to this list by submitting a pull request.
 ### Tools, Techniques & Libraries
 
 * [re-fill](https://github.com/metosin/re-fill) - routing and more  
-* [re-frame-undo](https://github.com/Day8/re-frame-undo) - An undo library for re-frame
-* [re-frame-test](https://github.com/Day8/re-frame-test) - Advanced testing utilities
+* [re-frame-undo](https://github.com/day8/re-frame-undo) - An undo library for re-frame
+* [re-frame-test](https://github.com/day8/re-frame-test) - Advanced testing utilities
 * [Animation](http://www.upgradingdave.com/blog/posts/2016-12-17-permutation.html) using `react-flip-move`
 * [re-thread](https://github.com/yetanalytics/re-thread) - A library for running re-frame applications in Web Workers.
 * [re-frame-datatable](https://github.com/kishanov/re-frame-datatable) - DataTable UI component built for use with re-frame.
@@ -85,7 +85,7 @@ Please add to this list by submitting a pull request.
 #### Debugging
 
 
-* [re-frame-10x](https://github.com/Day8/re-frame-10x) - A debugging dashboard for re-frame
+* [re-frame-10x](https://github.com/day8/re-frame-10x) - A debugging dashboard for re-frame
 * [re-frisk](https://github.com/flexsurfer/re-frisk) - A library for visualizing re-frame data and events.
 
 #### React Native

docs/External-Resources.md

@@ -4,7 +4,7 @@ How can I detect exceptions in Event Handlers?
 
 ### Answer
 
-A suggested solution can be found in [this issue](https://github.com/Day8/re-frame/issues/231#issuecomment-249991378).
+A suggested solution can be found in [this issue](https://github.com/day8/re-frame/issues/231#issuecomment-249991378).
 
 ***
 

docs/FAQs/CatchingEventExceptions.md

@@ -10,7 +10,7 @@ These libraries might be interesting to you:
   - [SubGraph](https://github.com/vimsical/subgraph)
   - [pull](https://github.com/juxt/pull)
 
-See also [this comment](https://github.com/Day8/re-frame/issues/304#issuecomment-269620609).
+See also [this comment](https://github.com/day8/re-frame/issues/304#issuecomment-269620609).
 
 If you want to go whole hog and ditch `app-db` and embrace DataScript, 
 then you might find [re-posh](https://github.com/denistakeda/re-posh) interesting.

docs/FAQs/DB_Normalisation.md

@@ -8,7 +8,7 @@ If at a REPL, inspect:  `re-frame.db/app-db`.
 
 If at the js console, that's `window.re_frame.db.app_db.state`.
 
-If you want a visual browser of app-db, along with inspecting subpaths of app-db, and diffing changes, use [re-frame-10x](https://github.com/Day8/re-frame-10x).
+If you want a visual browser of app-db, along with inspecting subpaths of app-db, and diffing changes, use [re-frame-10x](https://github.com/day8/re-frame-10x).
 
 You are [using cljs-devtools](https://github.com/binaryage/cljs-devtools), right? 
 If not, stop everything ([unless you are using re-natal](https://github.com/drapanjanas/re-natal/issues/137)) and immediately make that happen. 

docs/FAQs/Inspecting-app-db.md

@@ -35,7 +35,7 @@ low level operation performed in the service of fulfilling
 the user's intent.
 
 There's a useful effect handler available for HTTP work:
-https://github.com/Day8/re-frame-http-fx
+https://github.com/day8/re-frame-http-fx
 
 Look at the "Real World App" example for inspiration: 
 https://github.com/jacekschae/conduit

docs/FAQs/LoadOnMount.md

@@ -37,7 +37,7 @@ There are three ways to view this:
      within a map-ish structure (a `registrar`), once, on program load.
      So, if you feel uncomfortable with what re-frame does, you should also feel uncomfortable about using `defn`.
      Also, it would be useful to understand 
-     [how you are creating a virtual machine when you program re-frame](https://github.com/Day8/re-frame/blob/master/docs/MentalModelOmnibus.md#on-dsls-and-machines)   
+     [how you are creating a virtual machine when you program re-frame](https://github.com/day8/re-frame/blob/master/docs/MentalModelOmnibus.md#on-dsls-and-machines)   
 
 
 While Point 3 is an interesting perspective to consider, the real discussion should probably be around points 1 and 2: is it a good idea for re-frame to tradeoff purity for simplicity?  You can't really judge this

docs/FAQs/ViewsOnGlobalRegistration.md

@@ -4,7 +4,7 @@ How long after I call `dispatch` will the event be processed?
 
 ### Answer
 
-The answer is "it depends", but [this comment in the code](https://github.com/Day8/re-frame/blob/master/src/re_frame/router.cljc#L8-L60)
+The answer is "it depends", but [this comment in the code](https://github.com/day8/re-frame/blob/master/src/re_frame/router.cljc#L8-L60)
 might provide you the answers you seek.  
 
 

docs/FAQs/When-Does-Dispatch-Happen.md

@@ -13,7 +13,7 @@ The trailing `c` in `.cljc` stands for `common`.
 Necessary interop for each platform can be found in
 `interop.clj`  (for the JVM)  and `interop.cljs` (for JS).
 
-See also: https://github.com/Day8/re-frame-test
+See also: https://github.com/day8/re-frame-test
 
 
 ***

docs/FAQs/Why-CLJC.md

@@ -22,8 +22,8 @@ y'know. Pretty good.
 
 
 [![Clojars Project](https://img.shields.io/clojars/v/re-frame.svg)](https://clojars.org/re-frame)
-[![GitHub license](https://img.shields.io/github/license/Day8/re-frame.svg)](license.txt)
-[![Circle CI](https://circleci.com/gh/Day8/re-frame/tree/master.svg?style=shield&circle-token=:circle-ci-badge-token)](https://circleci.com/gh/Day8/re-frame/tree/master)
+[![GitHub license](https://img.shields.io/github/license/day8/re-frame.svg)](license.txt)
+[![Circle CI](https://circleci.com/gh/day8/re-frame/tree/master.svg?style=shield&circle-token=:circle-ci-badge-token)](https://circleci.com/gh/day8/re-frame/tree/master)
 
 ## re-frame
 

docs/INTRO.md

@@ -381,7 +381,7 @@ And some Interceptor factories (functions that return Interceptors):
   - __after__: perform side effects, after a handler has run.  Eg: use it to report if the data in `app-db` matches a schema.
   - __path__:  a convenience. Simplifies our handlers. Acts almost like `update-in`.
 
-In addition, [a Library like re-frame-undo](https://github.com/Day8/re-frame-undo) provides an Interceptor
+In addition, [a Library like re-frame-undo](https://github.com/day8/re-frame-undo) provides an Interceptor
 factory called `undoable` which checkpoints app state.
 
 

docs/Interceptors.md

@@ -194,7 +194,7 @@ This assumes boolean flags are set in `app-db` when data was loaded from these s
 In simple cases, you can simplify matters by using `dispatch-sync` (instead of `dispatch`) in 
 the main function.  
 
-This technique can be seen in the [TodoMVC Example](https://github.com/Day8/re-frame/blob/master/examples/todomvc/src/todomvc/core.cljs#L49).
+This technique can be seen in the [TodoMVC Example](https://github.com/day8/re-frame/blob/master/examples/todomvc/src/todomvc/core.cljs#L49).
 
 `dispatch` queues an event for later processing, but `dispatch-sync` acts 
 like a function call and handles an event immediately. That's useful for initial data