with nip34 in its current state there is no way to identify the root
patch without first requesting all patches and client side filtering
out the ones with `[ PATCH n/n ]` in
the content
this commit doesn't do that filtering
- display the commit message from the patch content if description tag
is not present
- fix '[unknown commit id]' display
to run typescript tests ts-ject was added as a dev dependancy
- get event pubkey in using correct parameter name
- get r tag value for unique_commit
- extract t tags
a typeguard is require like in ngit to ensure the r tag is
formatted as unique_commit
- update repo event maintainers format to reflect model used for
multiple entries for a single tag used in nip34
- show all users claiming to be a maintainer of identifier on homepage
- update repo event tags to reflect nip34
- refactor: move RepoSummary interface and default into type.ts
the notable visible change is to use `clone` tag in place of
`git_server`
non-nip34 tags are supported: `unique_commit` and `maintainers`.
these enable desirable functionality to be maintained.
this option reduces the size of the avatar so that it doesn't effect the
line height. note this only works at the text size / line-height
where the component is currently used.
temporary solution to users who accidentally ran `ngit claim` on a repo
they didn't own
ngit will select the version listed in `maintainers.yaml` if present but
git together doesn't have a trusted copy of the underlying repo to find
the correct `maintainers.yaml`
presenting multiple options for the user combined with a staring /
following system linked with WoT is the long term plan
This applies a really basic version of the parsing in
ndk-svelte-components which was copied from coracle. hopefully they can
be fully aligned in the future. I applied extra typing and will
intergrate other ParsedParts when needed.
applied line breaks to commit messages, pr description and default for
event content.
snort.social does not accept events from users without a subscription
whereas nos.lol does. This makes it a more likely to have more git
related events
prevent bug where PR responses and summaries are added to an incorrect
pr or repo after the array has been cleared but before
ensureSelectedRepo has returned
DanConwayDev
jk
DanConwayDev
jk