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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
rfc: integrating with [payment] service providers apps #3929
base: master
Are you sure you want to change the base?
Conversation
File provider extension has these limitations: | ||
- it has to run within 25 mb memory (other extensions have the same limit). | ||
- it is a separate process, and unless the provider app already uses shared files and shared database it may require some re-engineering to move app data to shared container of the app's app group. | ||
- it has to use files, as while it's possible to use a "fake file" simply to create a service, it would not be compliant with app store policies. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
quickly searched for policy but didn't find what this refers to.. not sure masquerading api calls as files wouldn't constitute as fake files, if they specifically mean files in common meaning of user files.
requests: # request templates | ||
- spec: invoice_request # spec contains standardized template name that defines file schema | ||
versions: 1-3 # optional, to allow independently version specific templates and endpoints | ||
file: invoice_request.yml # app-defined name for template |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
file_suffix / suffix?
file: invoice_request.yml # app-defined name for template | |
file: invoice_request.yml # app-defined name for template |
No description provided.