angularjs - An issue with testing $resource service by $httpBackend -

-

मुझे लगता है मुझे कुछ याद आती है 

  angular.module ('services') .factory ('UserPreferencesService', [ '$ संसाधन', फ़ंक्शन ($ संसाधन) {रिटर्न $ संसाधन ('/ rest / user-preferences /: id', {}, {getById: {method: "GET", पैराम्स: {आईडी: 'आईडी'} }});}]);

परीक्षा: 

  इसे ('आईडी से प्राप्त करना चाहिए', फ़ंक्शन () {// दिया गया वरीयता = {भाषा: "एन"} ; HttpBackend.whenGET ('/ बाकी / उपयोगकर्ता-प्राथमिकताएं / 1')। प्रतिक्रिया (वरीयताएँ); // जब service.getById ({id: 1})। $ वादा। तब (फ़ंक्शन (परिणाम) {console.log ( "Successssssssssssssssssssssssssssssssssssssss"); // फिर उम्मीद है (परिणाम) .toqual (वरीयताएँ);}, फ़ंक्शन () {console.log ("कुछ गलत");})});

यह कभी भी चालू नहीं होता है: "successssssssssssssssssssssssssssssssssssss"।

मुझे क्या याद आया?

कुछ चीजें गलत थीं और अन्य चीज़ें गायब थीं आपके कोड में

मुख्य समस्या यह थी कि आप फ्लश () फ़ंक्शन को कॉल नहीं कर रहे थे जो कि सर्वर से प्रतिक्रिया को emulates करता है, इसलिए $ वादा कभी हल नहीं किया गया था । इसके अलावा, ध्यान रखें कि जब वादा का समाधान हो जाता है, तो आप जिस प्रतिक्रिया से वादा करता है, इसका मतलब यह है कि: उम्मीद (परिणाम) .केल (वरीयताएँ); काम नहीं करेगा, लेकिन यह: उम्मीद (result.lang) .toEqual (preferences.lang); होगा।

यहां आपके पास आपका कोड का एक निश्चित संस्करण है:

सेवा: 

  कोणीय। मॉड्यूल ('सेवाएं', ['एनजीआरएसओआरएस'])। फैक्टर ('यूजरफ्रीफिंससेवा', ['$ संसाधन', फ़ंक्शन ($ संसाधन)) रिटर्न $ संसाधन ('/ बाकी / उपयोगकर्ता-प्राथमिकताएं:: आईडी ', {}, {getById: {method: "GET", पैराम्स: {id:' id}}}});}]));

टेस्ट: 

  वर्णन ('मेरा सूट', फ़ंक्शन () {var httpBackend, सेवा; पहले (मॉड्यूल ('सेवाओं')); पहले (प्रत्येक (इंजेक्शन (_ $ httpBackend_, UserPreferencesService) {httpBackend = _ $ httpBackend_; service = UserPreferencesService;})) वर्णन करें ('मेरा टेस्ट', फ़ंक्शन () (यह ('आईडी के आधार पर होना चाहिए', फ़ंक्शन) {Var प्राथमिकताएं = {भाषा: "एन"}; var परिणाम = {}; httpBackend.whenGET ('/ बाकी / उपयोगकर्ता-प्राथमिकताएं / 1')। प्रतिक्रिया दें (प्राथमिकताएं); service.getById ({id: 1})। $ वादा। तब (कार्य (परिणाम_) {परिणाम = परिणाम_;}); उम्मीद है (परिणाम.भाषी) .नोट नहीं। प्रश्न (प्राथमिकताएं। भाषा); httpBackend.flush (); उम्मीद (परिणाम.भाषी)। भाषा);});});});


Comments

Post a Comment

Popular posts from this blog

c# - SignalR: "Protocol error: Unknown transport." when navigating to hub -

-
Image
I am trying to use the ASP.NET signal for the first time - here's what I did: created a new web Has been added to the project and the following signal R packages: I have created the following category: [Hub-name ("chat")] Public class ChatHub: Hub {Public Zero Halo () {Clients.All.hello ( ); }} and the following startup configuration: public partial class startup {public zero configuration (IAppBuilder app) {configure (app); App.MapSignalR (); }} However, whenever I navigate localhost: (port) / api / signalr / chat I get the following error: Protocol error: Unknown transport. I am running a new browser and trying different people so remove it from the API / URL, and just use the localhost: (potter) / signaller / Chat
Read more

Camel ProducerTemplate possible memory leak -

-
To some degree, this is a bit of a shot in the dark, but we have a process that is dramatically slow One day's course we have found that all the things running on the fuses begin to draw, but when we are running a specific process, JPPropellers are going on, I have found that the increase in magnetic usage increases over time. . Org.apache.camel.ProductTemplate.Send So my main question is, is the way in which the manufacturer product is being used here which is wrong / can this be a problem? exchange foo = new DefaultExchange (getCamelContext (), ExchangePattern.InOnly); Foo.getIn () setBody (obj). Root R = Exchange .getContext (). GetRoute ("do_something_fun"); Creator Template Template = exchange.getContext () CreateProducerTemplate (); Template.send (r.getEndpoint (), foo); Generally, you should not create a productive template on each request as described here: / P> However, because I do not have a complete picture of your application, so you can cr...
Read more

javascript - Adhering to a max length setting with jshint -

-
I get several recommendations to compile a maximum of 80 characters when writing javascript, e.g. Google, NPM, Node. JS, Crockford In some cases, though, I do not think how best to do this. MongoClient.connect ('mongodb: // localhost: 27017 / sampleDatabase', function (mistake, database) {if (err)} {throw error;} db = database;}); This will throw a jshint warning because it exceeds 80 characters. Now, do you choose to ignore the warning in this example, or instead choose an option for a solution like MongoClient.connect ('mongodb: // localhost: 27017 / sampleDatabase' , Function (err, database) {if (err) {throw error;} db = database;}); If you can reuse the url variable So, great option if this is a shot, as is often such a call, I would probably do something like this ... / * jslint sloppy: true, white: true, browser: True, maxlen: 80 * / / * global mongo client * / var dbarhh, db; DbErrHand = function (mistake, database) {if (err) {throw error; } ...
Read more