Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feat/lw 12074 enable new input resolver in lace #1639

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

AngelCastilloB
Copy link
Member

Checklist

  • JIRA - <link>
  • Proper tests implemented
  • Screenshots added.

Enable new Input resolver on Lace

Proposed solution

Add a new feature flag to toggle blockfrost input resolver on Lace

@AngelCastilloB AngelCastilloB requested a review from a team as a code owner January 10, 2025 12:47
@AngelCastilloB AngelCastilloB force-pushed the feat/lw-12074-enable-new-input-resolver-in-lace branch 3 times, most recently from 2a3ed68 to 5ae6f1b Compare January 10, 2025 12:59
@AngelCastilloB AngelCastilloB force-pushed the feat/lw-12074-enable-new-input-resolver-in-lace branch from 5ae6f1b to aafe57d Compare January 10, 2025 13:17
Copy link

@pczeglik-iohk
Copy link
Contributor

Allure Report

allure-report-publisher generated test report!

processReports: ✅ test report for aafe57d7

passed failed skipped flaky total result
Total 33 0 4 0 37

@@ -152,6 +173,16 @@ const walletFactory: WalletFactory<Wallet.WalletMetadata, Wallet.AccountMetadata
witnesser
}
);

if (inputResolver) {
inputResolver.setContext(sharedWallet);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(just an idea, not a change req) I think we had some kind of 'combineInputResolvers` function. It could be used instead of context approach

@AngelCastilloB AngelCastilloB marked this pull request as draft January 10, 2025 13:47
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.

3 participants