-
Notifications
You must be signed in to change notification settings - Fork 18
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
Remove meta resolver #380
Remove meta resolver #380
Conversation
385fc2e
to
9ec1348
Compare
Documentation looks very good and else the changes are fine, which cases where we have arbitrary payload data that we have to generally make available to the frontend, still exist now? @Mikearaya |
@pozylon yes, projects need to define their own explicit resolvers now and no meta field will be available for the listed types. meta will be available at a resolver definition point |
is there anything you think should be added to this? |
Meta Usage Today by the big shops:
|
b2374ac
to
0c9342d
Compare
I fixed some things with controlpanel and removed the order meta props, tests all running through |
each payment provider should implement a type for PaymentCredential meta to be removed DataTrans, Strip, etc... because each expect different fields