blocks|key|2808621|text|在最新的稳定版本(当前为1.0.6)中，ngResource不返回承诺。此外，它看起来比ngResource公开了更多的动词(它公开了PUT，OPTIONS，PATCH等)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2808622|如果你不需要额外的动词，并且正在使用AngularJS的不稳定分支(包括对ngResource的承诺)，我看不出有任何主要的理由在ngResource上使用Restangular。|2808623|使用任何你觉得舒服的东西。|2808624|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

ngResource does not return promises in the latest stable release (currently 1.0.6). Additionally, it looks like Restangular exposes more verbs than ngResource (it exposes PUT, OPTIONS, PATCH, etc).

If you don't need the additional verbs and are on the unstable branch of AngularJS (which includes promises for ngResource), I don't see any major reason to use Restangular over ngResource.

Use whatever you feel comfortable with.

blocks|key|187087|text|我是Restangular的创建者。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|187088|我已经创建了一个关于自述文件的部分，其中包含与$resource的区别。你可以在这里查看https://github.com/mgonto/restangular/blob/master/README.md#differences-with-resource|offset|length|187089|总之，总而言之，除了额外的功能和基于promise的方法之外，这个想法是Restangular还可以处理你所有的URL，所以你不需要知道任何关于它们的事情。|187090|假设您有这样的汽车:/users/123/car/456|187091|在$resource中，您必须手动构造URL，还必须为此手动构造$resource对象。Restangular通过“记住”URL来帮助你做到这一点。|187092|所以如果你在某个地方这样做|187093|Restangular.one("users",+123).get().then(function(user)+{
++$scope.user+=+user;
});

//+Some+other+code

//Automatically+does+the+request+to+/users/123/cars+as+it+remembers+in+which+object+you're+asking+it.
$scope.user.getList('cars')|code-block|syntax|javascript|187094|希望这能有所帮助！|187095|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/mgonto/restangular/blob/master/README.md#differences-with-resource^0|0|18|2D|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|13|8|@]|9|@$D|14|E|15|1|16]]|A|$]]|$1|F|3|G|5|6|7|17|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|18|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|19|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|1A|8|@]|9|@]|A|$]]|$1|N|3|O|5|P|7|1B|8|@]|9|@]|A|$Q|R]]|$1|S|3|T|5|6|7|1C|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|1D|8|@]|9|@]|A|$]]]|V|$W|$5|X|Y|Z|A|$10|11]]]]

I'm the creator of Restangular.

I've created a section on the README with the differences against $resource. You can check them out here <a href="https://github.com/mgonto/restangular/blob/master/README.md#differences-with-resource">https://github.com/mgonto/restangular/blob/master/README.md#differences-with-resource</a>

Anyway, as a sum up, besides the additional features and the promise based approach, the idea is that Restangular can also handle all of your URLs, so that you don't have to know anything about them.

Suppose that you have something like this for cars : /users/123/cars/456

In $resource, You'd have to construct that URL manually and you'd also have to construct the $resource object for this manually. Restangular helps you in this by "remembering" the URLs.

So if you do in some place

<pre><code>Restangular.one("users", 123).get().then(function(user) {
 $scope.user = user;
});

// Some other code

//Automatically does the request to /users/123/cars as it remembers in which object you're asking it.
$scope.user.getList('cars')
</code></pre>

Hope this helps!

blocks|key|191461|text|我发现Restangular的RequestInterceptor非常方便，可以在发出请求之前从对象中删除一些字段。我目前使用的大多数REST+webservices都不期望对象数据中的id出现在PUT请求中，而只是在url中。通常，他们不会期望不能通过PUT更新的额外数据字段(比如id，或者通过设置title等生成的slug+)。虽然我还没有想出如何用$resource以一种干净的方式做到这一点，但我发现这在Restangular中是很简单的，但我相信这是可能的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|191462|显然，您也可以将webservice更改为忽略这些额外的字段，但这并不总是可行的。|191463|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I found Restangular's RequestInterceptor quite handy to remove some fields from the object before making the Request. Most REST webservices i am currently working with don't expect the id in the object data in a PUT request for example, just in the url. Generally they don't expect extra data fields that can not be updated by PUT (like the id, or a slug which is generated by setting the title etc). I found this to be straightforward with Restangular while i haven't figured out how to do it with $resource in a clean way, but i am sure its possible somehow.

Obviously one could also change the webservice to just ignore those extra fields, but thats not always possible.

blocks|key|188620|text|作为上述答案的后续，以及像我这样对这些想法感兴趣的新读者：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|188621|如果发生这种情况，|188622|似乎将消失，变得无依无靠。|blockquote|188623|188624|“三个月后，当这个家伙因为谷歌的ngResource弥补了它所缺少的所有功能而放弃了对瑞士角的支持时，会发生什么？”|188625|188626|188627|在两年前问|unordered-list-item|188628|188629|在我看来，开源图书馆生存下来的唯一保证就是围绕它建立的社区。最好的例子是mariaDB和WebScaleSQL，它们都是作为伟大的关系数据库管理系统MySQL的一个不断发展的分支而诞生的。|188630|在写这篇文章的时候，Restangular现在正在向支持AngularJs2.0和ES6的Restarar2.0前进。|188631|会议讨论关于：https://github.com/mgonto/restangular/issues/890.|offset|length|188632|first+repo+|188633|
|188634|：mgonto提交的会议：https://youtu.be/fWar75R1NGo|188635|188636|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/mgonto/restangular/issues/890|1|https://youtu.be/fWar75R1NGo^0|0|0|0|0|0|0|0|0|0|0|0|7|1C|0|0|0|0|D|S|1|0|0^^$0|@$1|2|3|4|5|6|7|1E|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1F|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|1G|8|@]|9|@]|A|$]]|$1|G|3|-4|5|6|7|1H|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|1I|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|1J|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|1K|8|@]|9|@]|A|$]]|$1|L|3|M|5|N|7|1L|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|1M|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|1N|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|1O|8|@]|9|@]|A|$]]|$1|T|3|U|5|6|7|1P|8|@]|9|@$V|1Q|W|1R|1|1S]]|A|$]]|$1|X|3|Y|5|N|7|1T|8|@]|9|@]|A|$]]|$1|Z|3|10|5|6|7|1U|8|@]|9|@]|A|$]]|$1|11|3|12|5|N|7|1V|8|@]|9|@$V|1W|W|1X|1|1Y]]|A|$]]|$1|13|3|-4|5|6|7|1Z|8|@]|9|@]|A|$]]|$1|14|3|-4|5|6|7|20|8|@]|9|@]|A|$]]]|15|$16|$5|17|18|19|A|$1A|1B]]|1C|$5|17|18|19|A|$1A|1D]]]]

As a following up to the above answers and for new readers, like me, interested in those thoughts :

<blockquote>
 "And if that happens Restangular seems like it will disappear and become irrelivant."
 
 "What happens in three months when this guy drops support for
 Restangular because Google's ngResource caught up to all the features
 it was missing."
</blockquote>

<ul>
<li>[ asked 2 years ago ]</li>
</ul>

In my opinion the only guarantee to the survive of an open-source library is the community built around it. a best example would be mariaDB and WebScaleSQL which both of them were born as a growing fork to the great relational database management system MySQL.

At this writing time Restangular <code>having 6699 stars and 727 forks</code> is now moving forward to Restangular 2.0 which is meant to support angularJs 2.0 and ES6.

<ul>
<li>discussion about : <a href="https://github.com/mgonto/restangular/issues/890" rel="nofollow">https://github.com/mgonto/restangular/issues/890</a>.</li>
<li>first repo preview :
<a href="https://github.com/mgonto/restangular/tree/2.0-wip" rel="nofollow">https://github.com/mgonto/restangular/tree/2.0-wip</a></li>
<li>ng-europe conference presented by mgonto :
<a href="https://youtu.be/fWar75R1NGo" rel="nofollow">https://youtu.be/fWar75R1NGo</a></li>
</ul>

blocks|key|2808657|text|为了快速，简单的网站，你想永远运行与最低限度的支持，我会使用内置的角度http+HttpClient谁，当我在一个我喜欢的项目，我喜欢并试图使用所有酷的技术，然后我会使用Ngx-Restangular|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2808658|此外，您应该知道，ngx-+that只能与RESTful服务一起工作，顾名思义。因此，对于提供SOAP的服务，您将无法使用Ngx-Restangular|2808659|https://ngx-restangular.com/|2808660|也就是说，，我大部分时间都会使用ngx-restangular+，因为我总是尝试做我觉得很酷的项目，并尝试实现我认为最好的东西。|2808661|祝你好运！|2808662|entityMap|0|LINK|mutability|MUTABLE|url^0|14|A|2D|F|0|1P|F|0|0|S|0|0|5|R|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]|$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Z|8|@$9|10|A|11|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|12|8|@]|D|@$9|13|A|14|1|15]]|E|$]]|$1|J|3|K|5|6|7|16|8|@$9|17|A|18|B|C]]|D|@]|E|$]]|$1|L|3|M|5|6|7|19|8|@]|D|@]|E|$]]|$1|N|3|-4|5|6|7|1A|8|@]|D|@]|E|$]]]|O|$P|$5|Q|R|S|E|$T|I]]]]

For quick simple website that you want to run for ever with the minimum support I would use the built-in angular http HttpClient whoever when I'm working on a project that I love and I'm enjoying and trying to use all cool technologies then I'll use Ngx-Restangular

Also you should know that ngx-restangular work with RESTful services only as the name suggest. So for services that provide SOAP you will not be able to use Ngx-Restangular

<a href="https://ngx-restangular.com/" rel="nofollow noreferrer">https://ngx-restangular.com/</a>

That being said I would use ngx-restangular most the time as I always try to work on project that I find cool and try to implement what I think is best.

Best of luck!

<code>ngResource</code> already seems really simple to implement things with...

What are the Advantages / Disadvantages of using <a href="https://github.com/mgonto/restangular" rel="noreferrer">Restangular</a> over <a href="http://docs.angularjs.org/api/ngResource.$resource" rel="noreferrer">ngResource</a>?

1.1.3 <code>$resource</code> will return promises and can be implimented using <a href="https://stackoverflow.com/questions/16429832/callback-after-async-foreach-angularjs/16447884#16447884">latest PR commit</a>. Will future support be offered to <code>$resource</code> to support additional verbs that Restangular does? And if that happens Restangular seems like it will disappear and become irrelivant.

What is the advantage of using Restangular over ngResource?

数据库管理系统

数据库管理

数据库

MySQL

ngResource看起来已经很容易实现了……与相比，使用有哪些优点/缺点1.1.3 $resource将返回promises，可以使用实现。未来是否会为$resource提供支持，以支持Restangular所做的其他动词？如果发生这种情况，Restangular似乎会消失，变得无依无靠。

问与ngResource相比，使用Restangular有什么优势？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问与ngResource相比，使用Restangular有什么优势？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问与ngResource相比，使用Restangular有什么优势？
EN