fryorcraken.eth 952aadd7bb

fix(dns-discovery/peer-exchange): check if peer is already tagged ...

If we `continue` when the peer is already known by the `peerStore` then
the next step of checking the tags is useless (no tags if peer is not
known).

There are two ways around it:
1. either do nothing if peer is already in peer store
2. OR, do nothing if peer is in peer store and is already tagged

I opted for the second approach to ensure all peers are tagged properly.

2023-03-10 10:09:10 +11:00

..

src

fix(dns-discovery/peer-exchange): check if peer is already tagged

2023-03-10 10:09:10 +11:00

.eslintrc.cjs

feat!: implement peer exchange (#1027)

2022-12-07 11:35:30 +05:30

.prettierignore

feat!: implement peer exchange (#1027)

2022-12-07 11:35:30 +05:30

CHANGELOG.md

chore: update note in CHANGELOG and add missing (#1178)

2023-02-14 01:11:40 +01:00

package.json

chore: rename build-utils to avoid potential conflict

2023-03-07 16:44:57 +11:00

rollup.config.js

chore: rename build-utils to avoid potential conflict

2023-03-07 16:44:57 +11:00

tsconfig.dev.json

chore: extract exports path from package.json for rollup

2023-03-01 15:46:21 +11:00

tsconfig.json

chore: fix peer discovery peer-exchange (#1069)

2023-01-04 14:35:44 +05:30