| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
Fixes #128.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This seems to be a bit more reliable, although it'll probably take
a little more memory while serving larger files.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Just always resolving was causing some bugs.
|
|
|
|
|
|
|
|
|
|
|
|
Finally putting the 'step' in 'data-steps'!
|
|
|
|
This reverts commit e09e11f1b933fa67f07c9f5e4340466f89672c8b.
|
|
|
|
Cherry-picked from 63be025
|
|
...Instead of tangling it in from generateTrackInfoPage, page/track.js,
and top-level page evaluation itself. This is why sprawling is better!
|
|
Sprawling basically means tying a component to objects which
aren't directly passed to it. This is necessary for functions
like transformContent, which was *mostly* implemented here
(the multiline/lyrics modes are stubs, and a number of links
haven't been implemented yet).
|
