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

Numeric Type Does Not Work with Expected to Decimal #5569

Closed
lucashtc opened this issue Nov 6, 2018 · 7 comments
Closed

Numeric Type Does Not Work with Expected to Decimal #5569

lucashtc opened this issue Nov 6, 2018 · 7 comments

Comments

@lucashtc
Copy link

@lucashtc lucashtc commented Nov 6, 2018

Description

When using culture pt_BR, values ​​after comma are rounded

Demo

Demo

Your environment

  • Handsontable version: 6.1.1
  • Browser Name and version: Google Chrome 69.0.3497.81
  • Operating System: Windows 10

One detail is that the default pt-BR uses "," to separate decimal places

@AMBudnik

This comment has been minimized.

Copy link
Contributor

@AMBudnik AMBudnik commented Nov 9, 2018

Thank you for sharing even when I use this pattern pattern: '$0.0,000', and place more decimal places in my data I still have only 1 decimal (rounded) place.

@lucashtc

This comment has been minimized.

Copy link
Author

@lucashtc lucashtc commented May 15, 2019

Hello,
After some analysis I got a certain success in the format,
using more updated versions the number appears with R$ with the decimal places,
But when copying the number and paste the number appears in the format not expected.
New Exemple
If I change the format of { data: 'price_usd', type: 'numeric', numericFormat: { pattern: 'R$0,0.00', // Changed culture: 'pt-BR' }, allowEmpty: false },

for { data: 'price_usd', type: 'numeric', numericFormat: { pattern: 'R$0,0,00', // Changed culture: 'pt-BR' }, allowEmpty: false }, copy and paste it will appear the correct value, but the view of it in the handsontable is incorrect .

@lucashtc

This comment has been minimized.

Copy link
Author

@lucashtc lucashtc commented May 15, 2019

When editing the line the format is also incorrect

@AMBudnik

This comment has been minimized.

Copy link
Contributor

@AMBudnik AMBudnik commented May 15, 2019

Thank you for doing the investigation and setting up an example.

@aninde

This comment has been minimized.

Copy link

@aninde aninde commented Feb 7, 2020

@lucashtc this issue will be fixed with new release of 7.4.0 v. Where we updated numbro.
Brazilian real will render correctly.
https://jsfiddle.net/aninde/5qpexj3b/

@aninde

This comment has been minimized.

Copy link

@aninde aninde commented Feb 12, 2020

Still fixed on updated 7.4.0 v. https://jsfiddle.net/aninde/nL16epx0/

@AMBudnik

This comment has been minimized.

Copy link
Contributor

@AMBudnik AMBudnik commented Feb 12, 2020

Hey @lucashtc

the issue is gone in v 7.4.0 - published 10 minutes ago. Please update and share feedback if possible :-) Thanks!

@AMBudnik AMBudnik closed this Feb 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.