ApiHandler / ChainData refactoring #2951
Merged
Commits on May 29, 2024
-
ApiHandler / ChainData refactoring
Removed a lot of retry/reconnect logic from ApiHandler and ChainData, as it was spawning a lot of PJS instances, which also handling reconnects on its own. This change also properly adpots the idea of talking both to relay chain and to parachains, depending on queried data. With new logic, each ApiHandler instance governs an interface to a single chain, where it can switch endpoints and do reconnects on its own. `ApiHandler.getApi()` returns a PJS instance that should work, and will block in case we're reconnecting. PeopleApi endpoints now live in configs, instead of being hardcoded. Instead of passing around ApiHandlers, passing a ChainData instance now, as it contains both ApiHandlers instance now, and as it is an intended abstraction for it
-
-
Merge pull request #2953 from w3f/yuri/websocket-disconnect-config
apiPeopleEndpoints in kusama configs
-
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.