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

alice.pds.demo.boltless.dev / core

0

This repository has no description

0

core / appview / pages / templates

5 folders 5 files

at c861440dbf58166d44df36c97b2e9e5b8ee67cd2

Anirudh Oppiliappan lexicons: issue, issue state and comment 2y ago

lexicons: issue, issue state and comment Custom lexicon for issues, issue state (open, closed) and issue comments. The case with issue_at is a bit weird since we have a circular dependency: the issue record requires the issue_id, and the issue entry in the db requires the issue_at. To resolve this we write to the db without the issue_at, fetch the issue_id, create the issue record on the PDS, and then update the issue_at (with SetIssueAt). It's not great, but whatever.

2 years ago

clean up timeline

2 years ago

implement issues and comments

2 years ago

better templates i guess

2 years ago

clean up timeline

2 years ago

appview: proper nested templates This now allows for a more organized template structure. All templates can now be accessed via "parent/child" paths, and are templated atop the layouts/*.html files. The layout files themselves are modular and can be included in each other. The only caveat is layout/*.html NEED to define their own template names like so: {{ define "base" }} The other page templates do not (and musn't) define their own template.

2 years ago

more htmxing

2 years ago

all: use securejoin

2 years ago

more htmxing

2 years ago

lexicons: issue, issue state and comment Custom lexicon for issues, issue state (open, closed) and issue comments. The case with issue_at is a bit weird since we have a circular dependency: the issue record requires the issue_id, and the issue entry in the db requires the issue_at. To resolve this we write to the db without the issue_at, fetch the issue_id, create the issue record on the PDS, and then update the issue_at (with SetIssueAt). It's not great, but whatever.

2 years ago