core/appview/pages/ at a008c1e78c779c3e29e16fd782072165319d5fc5 · alice.pds.demo.boltless.dev/core · Tangled

alice.pds.demo.boltless.dev / core

0

This repository has no description

0

core / appview / pages

3 folders 4 files

at a008c1e78c779c3e29e16fd782072165319d5fc5

oppiliappan appview/pages: rework caching mechanism 1y ago

appview: add support for latex in markdown Signed-off-by: noClaps <git@zerolimits.dev>

1 year ago

appview: stream logs from workflow endpoint Signed-off-by: oppiliappan <me@oppi.li>

1 year ago

appview/pages: refactor fragments to be one-per-file this is a limitation of how fragments are loaded at the moment. multiple definitions per file are unsupported. Signed-off-by: oppiliappan <me@oppi.li>

1 year ago

appview/pages: rework caching mechanism instead of loading all templates at once and storing into a map, we now memoize the results of `parse`. the first call to `parse` will require calculation but subsequent calls will be cached. this is simpler to reason about because the new execution model requires us to parse differently for each "base" template that is being used: - for timeline, it is necessary to parse with layouts/base - for repo-index, it is necessary to parse with layouts/base and layouts/repobase in that order the previous approach to loading also had a latent bug: all layouts were loaded atop each other in alphabetical order (order of iteration over the filesystem), and therefore it was not possible to selectively parse and execute templates on a subset of layouts. Signed-off-by: oppiliappan <me@oppi.li>

1 year ago

appview/{settings,pages}: rework settings ui Preserves the routes, but borrows a similar style to that of repo settings. Signed-off-by: Anirudh Oppiliappan <anirudh@tangled.sh>

1 year ago

appview: pages: Add HXRefresh helper function.

1 year ago

appview/pages: rework caching mechanism instead of loading all templates at once and storing into a map, we now memoize the results of `parse`. the first call to `parse` will require calculation but subsequent calls will be cached. this is simpler to reason about because the new execution model requires us to parse differently for each "base" template that is being used: - for timeline, it is necessary to parse with layouts/base - for repo-index, it is necessary to parse with layouts/base and layouts/repobase in that order the previous approach to loading also had a latent bug: all layouts were loaded atop each other in alphabetical order (order of iteration over the filesystem), and therefore it was not possible to selectively parse and execute templates on a subset of layouts. Signed-off-by: oppiliappan <me@oppi.li>

1 year ago