Issue with subscription to remove()
See original GitHub issueI’ve tried to subscribe to remove() to do some logging after removal of item and refreshing the grid. But I can’t subscribe to remove(). It’s send DELETE request and remove element from database. I get 200 - OK from server but on client I can’t hit subscribe method after that.
Could you help me somehow?
This is what I’ve tried:
restangular.one('Inventory', id).remove().subscribe( () => { console.log("blah") })
Issue Analytics
- State:
- Created 7 years ago
- Comments:5
Top Results From Across the Web
Remove a payment method from your Apple ID
Remove a payment method on your iPhone or iPad. Open the Settings app. Tap your name. Tap Payment & Shipping. Tap Edit, tap...
Read more >Delete a Pull Subscription - SQL Server - Microsoft Learn
This topic describes how to delete a pull subscription in SQL Server by using SQL Server Management Studio, Transact-SQL, or Replication ...
Read more >Create and use topics | Cloud Pub/Sub Documentation
This document explains how to create, update, view, and delete a Pub/Sub topic. This document also explains how to name topics and subscriptions....
Read more >Remove Proxmox Subscription Notice (Tested to 7.1-10)
To remove the “You do not have a valid subscription for this server” popup message while logging in, run the command bellow. You'll...
Read more >Deleting an Amazon SNS subscription and topic
Sign in to the Amazon SNS console . ... In the Delete subscription dialog box, choose Delete. The console deletes the subscription. When...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Since the problem was in the response (which is waiting for an object to return), I got the idea of the interceptor and used the response interceptor instead:
That implementation worked for me. 😃
Hi @cadin81, @bojanfbm we updated Restangular. Now we handle it in default response interceptor.