proposals / issues are fetched that tag the repo address pointer
for each maintainer listed in the selected repo event. not just the
ones that tag the selected proposal event.
previously, the link to each proposal would change the selected
repository to the first address pointer tagged in the proposal event
not only is the selected repo changing without the user's knowledge,
it can also cause an error if it points to a repo event that doesn't
exist. this happned here:
nostr:note1h25kwpycszl33285exdkrm4qz7a03e37nf4ujvexwqz94yj3k4xql9yj23
this ensures that the selected repo address pointer doesnt change.
if the proposal is accessed via gitworkhop.dev/e/<ref> the page will
error. a seperate change is needed to check through each
address pointer listed until it finds one that points to an actual
event.
issue:
nostr:note10kkr6mnj0wulfpenqeq02rzraxfj6yttk8lnfkz6lau9w7jeqldsjjwfla
this adds robustness to previous commit
ensureRepo always returns with writable that includes identifier and
author before any events are fetched
as reported in
nostr:nevent1qvzqqqqqqypzptssprfrjv9hwmqcpyhka26pujcflnelq0ekgxcmfehw82skd4mqqy88wumn8ghj7mn0wvhxcmmv9uq32amnwvaz7tmjv4kxz7fwv3sk6atn9e5k7tcqyrhp9z9j62llalp7j7ljhtkkr44j2ru24klh6wmfuhce8465pxavxtn8wk0
stop automatic grouping of repo events by identifer and
earliest unique commit into a single collection.
allow selection of different repos that have an
identifier collision by prioritising pubkey:identifier
over identifer
show repos grouped by name
to prevent repeated rendering of the same repository as a new item
nostr:nevent1qvzqqqqqqypzq3an3axnwgfep4dkhmmcmt3l8cug3mxm7xzylwenhzrjr5mx6hygqy88wumn8ghj7mn0wvhxcmmv9uq3vamnwvaz7tmsw4e8qmr9wfjkccte9e3k7mf0qqsdfpddg0e9k3k0k3tt7hkyemd936ec2wf6afufxn09hp42fq2q56qpxf7y4
as the https port will be different than that used by git
fix nostr:nevent1qqsv7mqkleadz5jzd63rygnne73ugh02wxuuq8evzcmlult4658dulspp4mhxue69uhkummn9ekx7mqzypl62m6ad932k83u6sjwwkxrqq4cve0hkrvdem5la83g34m4rtqeggv37pm
maintain subscription after eose for most events.
User events excluded as to prevent maintaining connections
to too many relays.
fixes nostr:nevent1qqs83c56u0vvggqq8skve94u783v9r4nmh0xw32wta29rt3ge3d04dspp4mhxue69uhkummn9ekx7mqzyzsq3hh327t0h2dq6matqn5064cgj2zanl2stkj6s0lg4t2h5dty6hju4ax
up the page so it is alway above the fold
closes nostr:nevent1qqs8cky62ry97jpaduja3urau75rr965jlrxswx6fpxa0nff22x2avspp4mhxue69uhkummn9ekx7mqzyquhg9lcgu6dq8pwn04ald504k4qpxde9e5rrlelfc0d2nkgj0k77ndyh60
and link to it whenever the UserHeader is displayed.
closes issue:
nostr:nevent1qqsyxwvgdaacc3hcd9rjwmjwqsfpu8guhrj37026ntl3aqw02mrprsgpzemhxue69uhhyetvv9ujumn0wd68ytnzv9hxgq3ql5sga6xg72phsz5422ykujprejwud075ggrr3z2hwyrfgr7eylqseukj7u
and partially fulfills issue:
nostr:nevent1qqsyxwvgdaacc3hcd9rjwmjwqsfpu8guhrj37026ntl3aqw02mrprsgpzemhxue69uhhyetvv9ujumn0wd68ytnzv9hxgq3ql5sga6xg72phsz5422ykujprejwud075ggrr3z2hwyrfgr7eylqseukj7u
as a temporary measure to prevent a wall of json
if this information is displayed at all it should be in the footer
of the event rather than amoung the replies
the dropdown icon was present but the selector component wasn't used
the selector options appeared without padding in header so this was
added in the component
fixes
https://gitworkshop.dev/repo/gitworkshop/issue/
7a8983734d366ae22828b4bbcc5c292480f427ab9f5a78428aa6fca1c9562b7b
Stuart D. Gathman
DanConwayDev
Alejandro Gómez