-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Render shipping cost nanos in emailservice #567
Conversation
|
The template used for the confirmation email in the emailservice did not render the nanos of the shipping cost. This commit adds them, so the rendering of shipping cost and item cost (lower in the template) is equivalent.
bd70d8b
to
63948eb
Compare
Hello @jjatria, thanks for the contribution. |
I don't think it is: the email is being sent through a test transport which as far as I understand does not actually send the email anywhere, it simply stores it for later inspection... which I don't think we do. I spotted the bug in the code rather than in the output, and if you look back at bc0cd67 to when the original Python version was ported to Ruby, you can see that the original was actually using the Looking at that commit now, it looks like the Ruby version is much less careful about how those numbers are printed, but I chose to keep the diff minimal and simply keep the two uses consistent. |
Ah great! |
@jjatria Thanks! I think this was just an oversight from when I initially added the ruby bits (but never noticed because as you pointed out: we don't really send any emails 😆 ) |
@ahayworth Makes sense! I only noticed this when I was porting this service to Perl so I could play around locally, and even then only when I noticed I was stringifying a hash instead of a number |
Changes
The template used for the confirmation email in the emailservice did not render the nanos of the shipping cost. This commit adds them, so the rendering of shipping cost and item cost (lower in the template) is equivalent.
This is a minor fix.