alpha
Login
or
Join now
alice.pds.demo.boltless.dev
/
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.
This repository has no description
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
2
Pulls
1
Pipelines
core
/
appview
/
pages
4 folders
5 files
at
442e2ab1b4dc3a8a75910abc564da55a639a495c
Seongmin Lee
appview: backlinks
9mo ago
442e2ab1
legal
appview/pages: add a brand page Also some misc. changes to page layouts. Signed-off-by: Anirudh Oppiliappan <anirudh@tangled.org>
11 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>
9 months ago
repoinfo
appview: remove unused fields on `RepoInfo` Signed-off-by: Seongmin Lee <git@boltless.me>
9 months ago
templates
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>
9 months ago
cache.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>
9 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>
9 months ago
funcmap_test.go
ci: fix nits Signed-off-by: oppiliappan <me@oppi.li>
10 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>
9 months ago