-
Notifications
You must be signed in to change notification settings - Fork 64
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
Server side refresh not working when using Post #219
Comments
Same here. Did you manage do get it working? |
The work around I did in the end was to add a new watch to a property on tasty table, when the property changed it triggered the server side code to execute the fetch. So I made the following changes:
It seems a bit hacky but at the moment it works :) Hope it helps! |
Thanks! could you send me your edited file? I really struggle with the implementation or could you answer me following questions, according your approach?
|
I made the changes in the ng-tasty-tpls.js file |
It works, thanks you! :) |
Hi,
We are using the ng-tasty table with the server side data option. The getResource functionality works fine with pagination and sorting etc. until I add ...
... to allow to force a reload of the data (after I delete a record) and then it stops rendering any data at all!
The server side end point is expecting a Http POST to get the data with the table required parameters in the payload from the paramsObj parameter.
I have followed the example from the documentation site and as far as I can see it's due to the POST instead of GET methodology of getting the data.
I think I've narrowed it down to ... https://github.com/Zizzamia/ng-tasty/blob/v0.6.1/src/component/table.js#L226
... as it seems to only set the $scope.url with building up a query string and not using paramsObj however I can't get it to fire off the $scope.reload() function to use the resourceCallback.
How can I get it to work with POST? Is there a way to hook directly into the setDirectivesValues function on the TableController to force the refresh?
Thanks
The text was updated successfully, but these errors were encountered: