-
Notifications
You must be signed in to change notification settings - Fork 21
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
pydocusign provides templates of DocuSign's notification callbacks #14
Comments
When I think about templates, I think about Jinja2 or other template engines. But this would be a dependency used for test purpose only. So as a developer, in order to run my pydocusign-based application, I would install (automatically, as a pydocusign's dependency) Jinja2, even if I do not use it at runtime. |
Isn't it a bit overkill? An option for this issue would be to use http://diecutter.io template rendering service:
Third-party pydocusign-based applications would also be able to use these resources online: diecutter with templates provided by pydocusign. A drawback of this solution would be performance: generating files using online templates and online HTTP service is slower than generating files using local templates and local software. Another drawback would be to depend on online service availability. |
Proposal:
|
…using templates. Improved template to support more events.
…gnCallbackParser that use callback template.
…red pseudo-constants for envelope and recipient events in models.
As a developer of software that uses DocuSign API via pydocusign,
in order to test the behaviour of an HTTP service that receive DocuSign's notification callbacks,
I want to fake these DocuSign's notification requests.
I do not want to follow a complete DocuSign workflow, mostly because:
So, I'd like the following things:
The text was updated successfully, but these errors were encountered: