-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
onCellValueChanged validate data using FETCH call to server. #3122
Labels
Comments
Hi, ag-grid staff does not provide support through github. If you are a customer please contact us through our official support channel. Note that this issue has been flagged as managed-by-the-community, we also recommend you to check stackoverflow, note that if there is no activity on this issue after a while we will close it. Thanks |
This is basically a pre-sales question. |
This was referenced Dec 8, 2021
This was referenced Dec 28, 2021
This was referenced May 13, 2022
This was referenced Nov 29, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm submitting a ...
Providing a Reproducible Scenario
I'm making a FETCH call to my API server in
onCellValueChanged
which modifies the server data. I validate sent data on the server and send back the appropriate response.I am using a custom React component (basic styled text input) for my
cellEditor
.Current behavior
Response of 200 is working well and I have no issues there. The data entered in the editor is rendered when tabbing away from the cell.
The cell value changes, but the data on the server remains unchanged as the payload to my API is rejected from validation (expected). eg.
A payload of a string is sent, but the server rejects a payload because the length of it is greater than accepted.
Expected behavior
If I get a response status of 4xx, then I want show a warning somewhere and not commit the data to the grid, leaving the cell in an editing state.
Please tell us about your environment:
ag-grid in React
Browser:
ALL
Language: ES6/7
The text was updated successfully, but these errors were encountered: