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

Add explicit extension point to matching algo #470

Closed
zkoch opened this issue Mar 23, 2017 · 7 comments
Closed

Add explicit extension point to matching algo #470

zkoch opened this issue Mar 23, 2017 · 7 comments

Comments

@zkoch
Copy link
Contributor

zkoch commented Mar 23, 2017

^^

@adrianhopebailie
Copy link
Collaborator

#492

@adrianhopebailie
Copy link
Collaborator

adrianhopebailie commented May 11, 2017

At the WG call on 11 May the @adrianba agreed to propose a different PR (to supersede #492).

@marcoscaceres
Copy link
Member

Postponing until after CR.

@ianbjacobs
Copy link
Collaborator

@marcoscaceres and @adrianba, would you mind providing rationale for the postponement? Thank you,

Ian

@marcoscaceres
Copy link
Member

There has been no movement on it for many months and it's unstable for the purpose of CR. Also, I think we can solve it in the Handler spec, because basic-card handlers and proprietary handlers can, theoretically, already do everything without needing this "hook".

@marcoscaceres
Copy link
Member

s/unstable/untestable... autocorrect 🤦‍♂️

@marcoscaceres
Copy link
Member

Closing this, as I think we can easily add it when we actually need it (i.e., once we pivot back to payment handler and work out exactly, if anything, we need).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants