js-waku/packages
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
..
build-utils chore: rename build-utils to avoid potential conflict 2023-03-07 16:44:57 +11:00
core feat: export `Decoder`, `Encoder` and `DecodedMessage` types from root 2023-03-08 09:52:27 +11:00
create chore: rename build-utils to avoid potential conflict 2023-03-07 16:44:57 +11:00
dns-discovery fix(dns-discovery/peer-exchange): check if peer is already tagged 2023-03-10 10:09:10 +11:00
enr chore: rename build-utils to avoid potential conflict 2023-03-07 16:44:57 +11:00
interfaces chore(deps)(deps-dev): bump @typescript-eslint/eslint-plugin 2023-03-06 23:23:40 +00:00
message-encryption feat: export `Decoder`, `Encoder` and `DecodedMessage` types from root 2023-03-08 09:52:27 +11:00
peer-exchange fix(dns-discovery/peer-exchange): check if peer is already tagged 2023-03-10 10:09:10 +11:00
proto chore: rename build-utils to avoid potential conflict 2023-03-07 16:44:57 +11:00
tests feat: export `Decoder`, `Encoder` and `DecodedMessage` types from root 2023-03-08 09:52:27 +11:00
utils chore: rename build-utils to avoid potential conflict 2023-03-07 16:44:57 +11:00