alpha
Login
or
Join now
oyster.cafe
/
tangled-core
forked from
tangled.org/core
Star
0
Fork
0
Atom
Configure Feed
Issues
Pull Requests
Commits
Tags
Feed URL
Select the types of activity you want to include in your feed.
Monorepo for Tangled
Star
0
Fork
0
Atom
Configure Feed
Issues
Pull Requests
Commits
Tags
Feed URL
Select the types of activity you want to include in your feed.
Overview
Issues
Pulls
Pipelines
tangled-core
/
appview
/
pages
/
at
da28eba8712005107a7eeaced7c634e26f04b0df
4 folders
5 files
Jens Rømer Hesselbjerg
appview/pages: decrease spacing between languages in repo summary
6mo ago
ca8217e9
legal
appview/pages: add a brand page Also some misc. changes to page layouts. Signed-off-by: Anirudh Oppiliappan <anirudh@tangled.org>
9 months ago
markup
appview: parse reference links from markdown body Defined `refResolver` which will parse useful data from markdown body like @-mentions or issue/pr/comment mentions Signed-off-by: Seongmin Lee <git@boltless.me>
7 months ago
repoinfo
appview: remove unused fields on `RepoInfo` Signed-off-by: Seongmin Lee <git@boltless.me>
7 months ago
templates
appview/pages: decrease spacing between languages in repo summary Signed-off-by: Jens Rømer Hesselbjerg <jh.roemer@gmail.com> Co-authored-by: Seongmin Lee <git@boltless.me>
6 months ago
cache.go
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>
10 months ago
funcmap.go
appview/pages: resolve did on render Don't pass resolved user handles from http handlers. The page renderer is capable of resolving DIDs and we are using redis cache, so the performance won't matter much either. Signed-off-by: Seongmin Lee <git@boltless.me>
7 months ago
funcmap_test.go
ci: fix nits Signed-off-by: oppiliappan <me@oppi.li>
8 months ago
htmx.go
appview: pages: Add HXRefresh helper function.
1 year ago
pages.go
appview: backlinks currently all backlinks are parsed with markdown parser. So only explict urls like below are supported: - <https://tangled.org/owner.com/repo-name/issues/123> - [full url](https://tangled.org/owner.com/repo-name/issues/123) - [absolute path](/owner.com/repo-name/issues/123) Also `#comment-123` fragment is supported too. All references in issue/pull/comment records are stored in at-uri format. we do have a `mentions` field, but it isn't used yet. mentions are parsed on rendering and aren't stored anywhere for now. Signed-off-by: Seongmin Lee <git@boltless.me>
7 months ago