Skip to content

feat: unseal Backend behind a custom-backend feature - #2279

Open
DenzelPenzel wants to merge 1 commit into
masterfrom
denzelpenzel/custom-backend-feature
Open

DenzelPenzel wants to merge 1 commit into
masterfrom
denzelpenzel/custom-backend-feature

Conversation

@DenzelPenzel

Copy link
Copy Markdown
Contributor

Summary

Split out of #2273 per review. The Backend trait is sealed, so external crates cannot provide their own Backend implementations. Enabling the new custom-backend feature unseals the trait, at the cost of its stability guarantees (new required methods may appear in minor releases).

The feature is named custom-backend rather than unstable-backend, since the latter was the historic name of the chain-head backend feature.

Implementation

  • A custom-backend feature flag on the subxt crate; without it the trait stays sealed.
  • An integration test implementing Backend externally with the feature enabled.
  • A UI test pinning that the trait remains sealed by default.
  • A CI job running the custom-backend tests.

The Backend trait is sealed by default. Enabling the new custom-backend
feature unseals it so that external crates can provide their own Backend
implementations, at the cost of the trait's stability guarantees. A UI
test pins the sealed-by-default behavior.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant