Hello team,
I am on a poc to validate the use of your components and I encounter a problem.
I'm using a "GridComponent" type component which works normally as long as it does something simple.
I need the "checkBoxChange" event, that works fine.
But when I save my file on visual studio code and the "hot reload" is done in the browser.
I have an error that blocks the page:
full log attached as well as part of my code.
Thank you.
Geoffrey
In the rest of my tests I wanted to add a template on an "emailConfirmed" column, and I think the two problems I have are related.
I attach my new test tsx file (simplified).
The crash happens when I click on the selection checkmark at the beginning of the line.
Am I forgetting something?
I'm on the latest version, updated yesterday.
After new tests this morning, finally even with a simple Grid, the "hot reload" makes the site explode...
I'm pretty sure of myself saying it's due to the update I made.
I made this update because when adding the template on a column I had the error: "str.match is not a function"
This is the only solution I found on your forums.
I have already performed these operations for the update:
I just redid them but the problem is still there.
I just tested with Edge and I have the same problem.
The only difference I see with the example you provide:
- I am with TypeScript and not JS
- I am in export default observer(function xx() {return()}) and not in export class CheckboxSelection{ render(){ return ()}}
Does this change anything?
I attach the package.json
Moreover as said above, even without the implementation of the "checkBoxChange" I have the problem.
The Grid is no longer usable after the "Hot reload" and this error is displayed
Attachment: package_27999293.zip
Hello,
I have something new.
This weekend, I started updating all my modules, so I am attaching my new package.json.
This error seems to have disappeared:
I keep getting this error when I click on a one line checkbox (It's the same error after a "hot reload")
:
in component-base.js (line 365):
FYI, I'm using React-router for the skeleton.
Thx
Geoffrey
Hello,
here is the answer that was given to me in Ticket 363330:
The reported issue occurs while Grid has columns with no specific field properties. Currently, we have forwarded this to the corresponding team. So, we will update the details on January 26th, 2022. Until then we appreciate your patience.
If it ever helps anyone else.