as requested in:
nostr:nevent1qvzqqqqqqypzpepndn2jthmelfxn4umylktqp493ph8yy9d2fse76al2ppprgjcsqy88wumn8ghj7mn0wvhxcmmv9uq3wamnwvaz7tmjv4kxz7fwdehhxarj9e3xzmny9uqzpu6lzfhs9xfjm8ue47mvvuxfwa3rm5v2fdd43ma6g47t7ssv7x70ed7vr6
even if the repo event doesn't exist there may be many issues
and proposal that reference it so it makes sence to:
1. show the repo Menu with a count of proposals and issues
2. show the details within the address point
2. show the issues and proposals page with a warning
RepoPageWrapper stops overwriting all content with error
RepoHeader show warning
RepoDetails show basic details from address point and a warning
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.
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
as the https port will be different than that used by git
fix nostr:nevent1qqsv7mqkleadz5jzd63rygnne73ugh02wxuuq8evzcmlult4658dulspp4mhxue69uhkummn9ekx7mqzypl62m6ad932k83u6sjwwkxrqq4cve0hkrvdem5la83g34m4rtqeggv37pm
and link to it whenever the UserHeader is displayed.
closes issue:
nostr:nevent1qqsyxwvgdaacc3hcd9rjwmjwqsfpu8guhrj37026ntl3aqw02mrprsgpzemhxue69uhhyetvv9ujumn0wd68ytnzv9hxgq3ql5sga6xg72phsz5422ykujprejwud075ggrr3z2hwyrfgr7eylqseukj7u
and partially fulfills issue:
nostr:nevent1qqsyxwvgdaacc3hcd9rjwmjwqsfpu8guhrj37026ntl3aqw02mrprsgpzemhxue69uhhyetvv9ujumn0wd68ytnzv9hxgq3ql5sga6xg72phsz5422ykujprejwud075ggrr3z2hwyrfgr7eylqseukj7u
store hexpubkey in Repo and Proposal data object
instead of full profile
this prevents unnecessary state updates for those objects
the trade-off is including business logic (getting profile data)
within UI components
this is mitigated by allowing hexpubkey or UserObject to be passed
to UI components so that UI component tests can be written without
having to worry about business logic
this new approach can be abstracted to other object types
turned off with feature stapling. requires:
* styles to be improved (inline image links, respecting html img sizing, etc)
* intergration into its own tab (potentially sepearte routing
for proposal, issues, readme)
* proxy to get readme via git for all git sources
choose repo events based from earliest_unique_commit and indentifier
based on:
- number of mentions (issues and root patches)
- most recent created_at
identify repo events for the same repository based on identical identifiers
and use of earliest_unique_commit
use stores for collections of repo events
- 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.
DanConwayDev
jk