diff options
| author | DanConwayDev <DanConwayDev@protonmail.com> | 2024-04-22 07:26:15 +0100 |
|---|---|---|
| committer | DanConwayDev <DanConwayDev@protonmail.com> | 2024-05-07 09:10:33 +0100 |
| commit | 10498b953d36304b441fcb162155c2487046206f (patch) | |
| tree | cea78cfbb83dbbe5ddae12ffde18df94ae7d6746 /src/git.rs | |
| parent | c4853f69dc25408ff70cccbe923d2cd400385fc2 (diff) | |
feat(send): `in-reply-to` tags npubs and events
in addition to being used to create a new proposal revision,
in-reply-to can now be used to reference other events and npubs.
for example an issues or kind 1 threads where the proposal is relevant
the proposal will only be marked as a revision if the first parameter is
a reference to an existing proposal root
Diffstat (limited to 'src/git.rs')
| -rw-r--r-- | src/git.rs | 2 |
1 files changed, 2 insertions, 0 deletions
| @@ -1526,6 +1526,7 @@ mod tests { | |||
| 1526 | None, | 1526 | None, |
| 1527 | None, | 1527 | None, |
| 1528 | &None, | 1528 | &None, |
| 1529 | &[], | ||
| 1529 | ) | 1530 | ) |
| 1530 | } | 1531 | } |
| 1531 | fn test_patch_applies_to_repository(patch_event: nostr::Event) -> Result<()> { | 1532 | fn test_patch_applies_to_repository(patch_event: nostr::Event) -> Result<()> { |
| @@ -1687,6 +1688,7 @@ mod tests { | |||
| 1687 | &TEST_KEY_1_KEYS, | 1688 | &TEST_KEY_1_KEYS, |
| 1688 | &RepoRef::try_from(generate_repo_ref_event()).unwrap(), | 1689 | &RepoRef::try_from(generate_repo_ref_event()).unwrap(), |
| 1689 | &None, | 1690 | &None, |
| 1691 | &[], | ||
| 1690 | )?; | 1692 | )?; |
| 1691 | 1693 | ||
| 1692 | events.reverse(); | 1694 | events.reverse(); |