Skip to content
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

Order summary values being stored as strings instead of decimals #3215

Closed
brent-hoover opened this issue Oct 31, 2017 · 0 comments
Closed

Order summary values being stored as strings instead of decimals #3215

brent-hoover opened this issue Oct 31, 2017 · 0 comments
Assignees
Labels
bug For issues that describe a defect or regression in the released software

Comments

@brent-hoover
Copy link
Collaborator

Expected behavior

Numbers should be stored as numbers

Actual behavior

Numbers stored as Strings

Steps to reproduce the behavior

  1. Place an order
  2. Open Robomongo or similar
  3. Go to billing/invoice and observe the values are stored as string

robo_3t_-_1_1

Additionally, the Schemas is set for validate these values are set to be decimals, however the entire billing/payment record is set to blackbox: true so the schema is ignored. There may be some items in payment we need to blackbox (like transactions) but we should reenabled as much of these schema validations as possible.

Versions

Node: 7.10.0
NPM: 5.4.2
Meteor Node: 4.8.4
Meteor NPM: 4.6.1
Reaction CLI: 0.19.1
Reaction: 1.5.4
Reaction branch: master
Docker: 17.09.0-ce
@brent-hoover brent-hoover added the bug For issues that describe a defect or regression in the released software label Oct 31, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug For issues that describe a defect or regression in the released software
Projects
None yet
Development

No branches or pull requests

2 participants