Fix Runtime API Discovery for PAPI #97
Merged
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.
This PR resolves the issue related to PAPI (Polkadot API) runtime API discovery.
PAPI Runtime API Discovery
During integration testing with PAPI, runtime APIs were not being detected in the PAPI console, and downloading descriptors consistently failed. For example, when running the following command:
The generated runtime API types were empty:
This issue was traced to changes in the Polkadot SDK (paritytech/polkadot-sdk#6665) where runtime API implementations were split into a dedicated
api.rsfile. While this worked within the SDK, it caused PAPI to fail in discovering and generating the runtime API types.Fix: All runtime API implementations were moved back from
api.rsintolib.rs. This change restored proper runtime API detection, and PAPI now successfully generates the expected IViewFns and IRuntimeCalls types.Issues Resolved
Summary of Changes
Impact