Validator error on the destination column of the endpoint cell of ColumnSummary

Tags: #<Tag:0x00007efc6d8d25f0>
#1

Hey,

I’ve created an instance of HandsOnTable and added ColumnSummary for one of its columns. If the type for the column is specified as ‘numeric’, the following error shows up on page load (PFA).

image
image.png1326×179 11.2 KB

However, I tried switching the type of the column to ‘text’ and the endpoint setting as forceNumeric: true and it worked but I’m still unable to validate that column using custom validator function (same as the one in the fiddle).

If I try applying the custom validator to the column, the same error pops up.

Furthermore, on replicating this using a fiddle, the issue didn’t occur. (handsontable-pro v6.2.3)

Link to fiddle (describing my requirement) : https://jsfiddle.net/hakstdLb/

Kindly suggest a suitable way to fix this.

Thanks,
Faiz

#2

Hey @faiz.tariq

I tried to narrow down the issue and took this demo https://handsontable.com/docs/7.2.1/demo-summary-calculations.html and just applied the type: ‘numeric’ to one of the columns https://jsfiddle.net/n1ugxa42/ but did not get the error and everything’s working as expected.

It also works well when I take your demo and change the TextRenderer to NumericRenderer https://jsfiddle.net/k8q3arfh/

Please guide me to how to replicate the error from the console.

#3

Hey Aleksandra,

Thanks for the quick response. Just to let you know that I’m facing this issue in my application which is built using Angular 6. I’ll try to create a demo of replication and get back to you in case if you can walk me through anything that is specific about Angular Wrapper for HandsOnTable, please do let me know.

Regards,
Faiz

#4

Usually when bugs are related to some kind of plugins they also happen on vanilla and any other wrapper (Vue, React).
Thank you for taking your time to create a demo.

#5

Hey,

Sorry for a late response. I’d figured out that the customRenderer function which was applied as a setting for the entire table was probably causing the issue. I tried applying it on individual columns and it did work for me and neither do I see the above error while calculating Summary nor do I face any validation/mis-calculation issues for the same.

Regards,
Faiz

#6

Thank you for the update, Faiz. I’m glad that you’ve found the cause of the issue.

#7