Skip to content

Client doesn't properly handle Text tabs with Date Validation #16

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

Closed
capitalist opened this issue Mar 14, 2019 · 9 comments
Closed

Client doesn't properly handle Text tabs with Date Validation #16

capitalist opened this issue Mar 14, 2019 · 9 comments
Labels

Comments

@capitalist
Copy link

Here's the tab from the template
Screenshot_3_14_19__17_13

And here's the parse error
Panel

@LarryKlugerDS
Copy link
Contributor

Hi @capitalist,
Thank you for the issue report.

Which SDK method were you using when the response from DocuSign couldn't be parsed?

Thank you,
Larry

@LarryKlugerDS
Copy link
Contributor

I have filed internal ticket DCM-3193.

Which SDK method were you using when the response from DocuSign couldn't be parsed?

@capitalist
Copy link
Author

Hey, sorry for being slow - I'll get you more details on the issue today.

@capitalist
Copy link
Author

capitalist commented Mar 20, 2019

Ok, I have it boiled down to it's essence.

The API call is simply a .get on an instance of the DocuSign_eSign::TemplatesApi

It's the template data that isn't parsed correctly, I can send you privately the template JSON that comes from the API if that helps.

@LarryKlugerDS
Copy link
Contributor

Thank you!

If you have time to confirm that removing the date validation makes the problem go away, that would be helpful since it would pinpoint that the date validation is what's triggering the bug.

Regards,
Larry

@capitalist
Copy link
Author

Confirmed:

image

image

@LarryKlugerDS
Copy link
Contributor

Many thanks for your time on the bug report.
Regards,
Larry

@capitalist
Copy link
Author

of course - thanks for the quick response!

@LarryKlugerDS
Copy link
Contributor

Good news, this issue has been fixed with the 3.0.0.rc.1 release of the SDK and gem. The source is available as branch ngopala/v2.1-19.2.02.

It will be released to master and the gem will be updated in the next week.

Please comment on this issue if you spot any issues with the RC (release candidate) or the forthcoming release.

Thanks,
Larry

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

No branches or pull requests

2 participants