refactor: use api3/chains for chain names in airnode-examples #1925
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #1741. Surprisingly, this was all that was needed, and the changes are covered by the tests below (and I confirmed in api3/chains that the network names are the same):
airnode/packages/airnode-examples/src/utils.test.ts
Lines 23 to 34 in b87e0b3
I checked throughout the repo for other instances where
references.json
ofairnode-protocol
is used for anything besides contract addresses (e.g. where we usechainNames
) and this was it. Airnode logs report "Chain-ID" (example) rather than chain name, and other references toreferences.json
are specific to addresses e.g. here in validator:airnode/packages/airnode-validator/src/config/config.ts
Lines 18 to 21 in b87e0b3