The problem was that `.success` and `.error` methods are **not chainable** because they **ignore return values**. This caused problems for people familiar with **chaining** and encouraged poor code from people unfamiliar with **chaining**. Witness all the examples on StackOverflow that use the [deferred anti-pattern][AntiPattern].

[AntiPattern]: https://stackoverflow.com/questions/30750207/is-this-a-deferred-antipattern

To quote one of the AngularJS team:
&gt;IMO `.success` and `.error` were a bad bit of API design in the first place. This issue highlights a number of situations where developers get confused because they either expect `.success` and `.error` to work the same way as `.then` or vice versa.
In a perfect world I would rather just ditch these `$http` specific &quot;promises&quot;. Instead we could encourage developers to use the standard `$q` promise API `.then` and `.catch`. There is very little benefit IMO in working with explicit parameters over working with the response object.

&gt;[&amp;#8212; AngularJS Issue #10508  `$http` `.success/.error` dissimilar from how `.then` works.](https://github.com/angular/angular.js/issues/10508)

&lt;!-- --&gt;

&gt;Deprecation Notice (v1.5)
&gt;--
&gt;The `$http` legacy promise methods `success` and `error` have been deprecated. Use the standard `then` method instead. If `$httpProvider.useLegacyPromiseExtensions` is set to `false` then these methods will throw `$http/legacy` error.

&gt;[&amp;#8212; AngularJS $http Service API Reference -- deprecation notice][DN]

[DN]: https://code.angularjs.org/1.5.10/docs/api/ng/service/$http#deprecation-notice

&lt;!--(https://docs.angularjs.org/api/ng/service/$http#deprecation-notice)--&gt;

----
UPDATE
--
The deprecated `.success` and `.error` methods have been removed from AngularJS 1.6.

&gt;Due to [b54a39](https://github.com/angular/angular.js/commit/b54a39e2029005e0572fbd2ac0e8f6a4e5d69014), `$http`&#39;s deprecated custom callback methods - `.success()` and `.error()` - have been removed. You can use the standard `.then()`/`.catch()` promise methods instead, but note that the method signatures and return values are different.

&gt;     $http(...)
      .then(function onSuccess(response) {
        // Handle success
        var data = response.data;
        var status = response.status;
        var statusText = response.statusText;
        var headers = response.headers;
        var config = response.config;
        ...
      }).catch(function onError(response) {
        // Handle error
        var data = response.data;
        var status = response.status;
        var statusText = response.statusText;
        var headers = response.headers;
        var config = response.config;
        ...
      });

&gt;[&amp;#8212; AngularJS Developer Guide - Migrating to v1.6 - http][HTTP]

[HTTP]: https://code.angularjs.org/snapshot/docs/guide/migration#migrate1.5to1.6-ng-services-$http


The pattern that javascript it using related to promises is only with `.then(successCallback, errorCallback)`, so they are probably aiming to use js pattern.

I want to drop my tables in my database.
But, when I use, for example,
`DROP TABLE if exists users;`
I receive this message:

&gt; `cannot drop table users because other objects depend on it`

I found the solution is to drop all tables. But, anyway, how to solve this problem without total data removal?

Cannot drop table users because other objects depend on it

I&#39;m using pyspark, loading a large csv file into a dataframe with spark-csv, and as a pre-processing step I need to apply a variety of operations to the data available in one of the columns (that contains a json string). That will return X values, each of which needs to be stored in their own separate column.

That functionality will be implemented in a UDF. However, I am not sure how to return a list of values from that UDF and feed these into individual columns. Below is a simple example:

    (...)
    from pyspark.sql.functions import udf
    def udf_test(n):
        return [n/2, n%2]

    test_udf=udf(udf_test)


    df.select(&#39;amount&#39;,&#39;trans_date&#39;).withColumn(&quot;test&quot;, test_udf(&quot;amount&quot;)).show(4)

That produces the following:

    +------+----------+--------------------+
    |amount|trans_date|                test|
    +------+----------+--------------------+
    |  28.0|2016-02-07|         [14.0, 0.0]|
    | 31.01|2016-02-07|[15.5050001144409...|
    | 13.41|2016-02-04|[6.70499992370605...|
    | 307.7|2015-02-17|[153.850006103515...|
    | 22.09|2016-02-05|[11.0450000762939...|
    +------+----------+--------------------+
    only showing top 5 rows

What would be the best way to store the two (in this example) values being returned by the udf on separate columns? Right now they are being typed as strings:

    df.select(&#39;amount&#39;,&#39;trans_date&#39;).withColumn(&quot;test&quot;, test_udf(&quot;amount&quot;)).printSchema()

    root
     |-- amount: float (nullable = true)
     |-- trans_date: string (nullable = true)
     |-- test: string (nullable = true)


Apache Spark -- Assign the result of UDF to multiple dataframe columns

The AngularJS documentation has a Deprecation Notice for the `$http` `success` and `error` methods. Is there a specific reason this abstraction was removed from the library?

Why are AngularJS $http success/error methods deprecated? Removed from v1.6?

<p>The AngularJS documentation has a Deprecation Notice for the <code>$http</code> <code>success</code> and <code>error</code> methods. Is there a specific reason this abstraction was removed from the library?</p>


I&#39;m just using simple input containers such as this

    &lt;md-input-container class=&quot;md-block&quot; flex-gt-sm &gt;
        &lt;label&gt;Name&lt;/label&gt;
        &lt;input md-maxlength=&quot;30&quot; name=&quot;name&quot; ng-model=&quot;name&quot; /&gt;
    &lt;/md-input-container&gt;

The input field is suggesting previously entered values which is obscuring some important interface elements and also really not necessary in my case. Is there any way to disable the suggestions?

Angular Materials: Can you disable the autocomplete suggestions for an input?

I have a float value for the ng-model that I would like to always display with 2 decimal places in the `&lt;input&gt;`: 

    &lt;input ng-model=&quot;myNumb&quot; step =&quot;0.01&quot; type=&quot;number&quot;&gt;

This works for most case when &quot;myNumb&quot; has decimal. But it will not force display of the 2  decimal places if &quot;myNumb&quot; has less than 2 decimal places (3.2), or an integer(30)  
How can I force a display of 2 decimal place in the `&lt;input&gt;` field

Display number always with 2 decimal places in &lt;input&gt;

I&#39;ve been upgrading my custom directives to the new [component architecture](https://docs.angularjs.org/guide/component#component-based-application-architecture). I&#39;ve read that components do not support watchers. Is this correct? If so how do you detect changes on an object? For a basic example I have custom component `myBox` which has a child component game with a binding on the game . If  there is a change game within the game component how do I show an alert message within the myBox? I understand there is rxJS method is it possible to do this purely in angular? My [JSFiddle][1]

**JavaScript**

    var app = angular.module(&#39;myApp&#39;, []);
    app.controller(&#39;mainCtrl&#39;, function($scope) {
        
       $scope.name = &quot;Tony Danza&quot;;
      
    });
    
    app.component(&quot;myBox&quot;,  {
          bindings: {},
          controller: function($element) {
            var myBox = this;
            myBox.game = &#39;World Of warcraft&#39;;
            //IF myBox.game changes, show alert message &#39;NAME CHANGE&#39;
          },
          controllerAs: &#39;myBox&#39;,
          templateUrl: &quot;/template&quot;,
          transclude: true
    })
    app.component(&quot;game&quot;,  {
          bindings: {game:&#39;=&#39;},
          controller: function($element) {
            var game = this;
            
           
          },
          controllerAs: &#39;game&#39;,
          templateUrl: &quot;/template2&quot;
    })
    
**HTML**

    &lt;div ng-app=&quot;myApp&quot; ng-controller=&quot;mainCtrl&quot;&gt;
      &lt;script type=&quot;text/ng-template&quot; id=&quot;/template&quot;&gt;
        &lt;div style=&#39;width:40%;border:2px solid black;background-color:yellow&#39;&gt;
          Your Favourite game is: {{myBox.game}}
          &lt;game game=&#39;myBox.game&#39;&gt;&lt;/game&gt;
        &lt;/div&gt;
      &lt;/script&gt;
      
     &lt;script type=&quot;text/ng-template&quot; id=&quot;/template2&quot;&gt;
        &lt;div&gt;
        &lt;/br&gt;
        	Change Game
          &lt;textarea ng-model=&#39;game.game&#39;&gt;&lt;/textarea&gt;
        &lt;/div&gt;
      &lt;/script&gt;
      
      Hi {{name}}
      &lt;my-box&gt;
        
      &lt;/my-box&gt;
      
    &lt;/div&gt;&lt;!--end app--&gt;


  [1]: https://jsfiddle.net/bkarv/swv22g3s/

AngularJS 1.5+ Components do not support Watchers, what is the work around?

In Angular 1.x I would sometimes need to make multiple `http` requests and do something with all the responses. I would throw all the promises in an array and call `Promise.all(promises).then(function (results) {...})`.

Angular 2 best practices seem to point towards the use of RxJS&#39;s `Observable` as a replacement to promises in `http` requests. If I have two or more different Observables created from http requests, is there an equivalent to `Promise.all()`?

Promise.all behavior with RxJS Observables?

I&#39;m on Windows 10, with Node 5.6.0 and npm 3.6.0. I&#39;m trying to install angular-material and mdi into my working folder. **npm install angular-material mdi** errors with:

    +-- angular@1.5.0

    +-- UNMET PEER DEPENDENCY angular-animate@^1.5.0

    +-- UNMET PEER DEPENDENCY angular-aria@^1.5.0

    +-- angular-material@1.0.6

    +-- UNMET PEER DEPENDENCY angular-messages@^1.5.0 `-- mdi@1.4.57

    npm WARN enoent ENOENT: no such file or directory, open
    &#39;C:\Users\xxxxx\Desktop\ngClassifieds\package.json&#39; 

    npm WARN angular-material@1.0.6 requires a peer of
    angular-animate@^1.5.0 but none was installed. 

    npm WARN angular-material@1.0.6 requires a peer of angular-aria@^1.5.0
    but none was installed. 

    npm WARN angular-material@1.0.6 requires a peer of
    angular-messages@^1.5.0 but none was installed.

How do I resolve this to get AngularJS Material and MDI installed?

How do I fix the npm UNMET PEER DEPENDENCY warning?

We have a pattern for resolving promises in our Angular app that has served us well up until Angular 1.6.0:

        resource.get().$promise
            .then(function (response) {
            // do something with the response
            }, function (error) {
                // pass the error the the error service
                return errorService.handleError(error);
            });

And here is how we are triggering the error in Karma:

        resourceMock.get = function () {
            var deferred = $q.defer();
            deferred.reject(error);
            return { $promise: deferred.promise };
        };

Now, with the update to 1.6.0, Angular is suddenly complaining in our unit tests (in Karma) for rejected promises with a &quot;Possibly unhandled rejection&quot; error. But we are handling the rejection in the second function that calls our error service.

What exactly is Angular looking for here? How does it want us to &quot;handle&quot; the rejection? 

Angular 1.6.0: &quot;Possibly unhandled rejection&quot; error

I was expecting to see this question on Stackoverflow but didn&#39;t. Apparently I&#39;m the only one having this problem that seems to me to be very common.

I have a basic project I am working on but the routes don&#39;t seem to work even though everything I&#39;ve done so far seems to be right.

I have this piece of html in my `index.html` file:

	&lt;html&gt;
	&lt;head ng-app=&quot;myApp&quot;&gt; 
		&lt;title&gt;New project&lt;/title&gt;
		&lt;script src=&quot;https://code.angularjs.org/1.6.0/angular.min.js&quot;&gt;&lt;/script&gt;
		&lt;script src=&quot;https://code.angularjs.org/1.6.0/angular-route.min.js&quot;&gt;&lt;/script&gt;

		&lt;script src=&quot;app.js&quot;&gt;&lt;/script&gt;
	&lt;/head&gt;
	&lt;body&gt;
		&lt;a href=&quot;#/add-quote&quot;&gt;Add Quote&lt;/a&gt;
		&lt;div ng-view &gt;&lt;/div&gt;
	&lt;/body&gt;
	&lt;/html&gt;

and here is my `app.js`:

    var app = angular.module(&#39;myApp&#39;, [&#39;ngRoute&#39;]);


	app.config([&#39;$routeProvider&#39;, function ($routeProvider) {
		$routeProvider
			.when(&#39;/add-quote&#39;, {
				templateUrl: &#39;views/add_quote.html&#39;,
				controller: &#39;QuoteCtrl&#39;
			})
			.otherwise({ redirectTo: &#39;/&#39; });
	}]);

Now when I just visit the page, here is what I get in the url:

&gt; http://localhost:8000/admin#!/

and when I click on the `Add quote` button, I get this:

&gt; http://localhost:8000/admin#!/#%2Fadd-quote

What can be the problem here?
Thanks for help

angularjs 1.6.0 (latest now) routes not working

My URLs on an AngularJS project have changed from `localhost:3000/admin#/` to `localhost:3000/admin#!/` since the last time I worked on my project...

Nothing found on the web, does someone know what this is ?


URL hash-bang (#!/) prefix instead of simple hash (#/) in Angular 1.6

I&#39;m having a massive problem with AngularJS routing.

Up until recently everything has been fine with the following route:

    $routeProvider.when(&#39;/album/:albumId&#39;, {
        controller: &#39;albumPageController&#39;,
        templateUrl: &#39;views/album.html&#39;
    });

and using the href:

    &lt;a href=&quot;/#/album/{{album.id}}&quot;&gt;Link&lt;/a&gt;

However, now all of the slashes are being encoded into `%2F`.

So when I click the link, or type `localhost:8000/#/album/1` into the browser, the URL is changed to:

&gt;http://localhost:8000/#%2Falbum%2F1

I&#39;ve tried several things to correct this:

Using ng-href instead of href, 
Not using the first / (ie `href=&quot;#/album/{{album.id}}&quot;`)
Running the app in Homestead localhost (Laravel&#39;s linux vagrant machine) instead of localhost on Windows 10

Any help would be much appreciated!

Content Type	Original Author	Original Content on Stackoverflow
Question	philoniare	View Question on Stackoverflow
Solution 1 - Angularjs	georgeawg	View Answer on Stackoverflow
Solution 2 - Angularjs	Igor Santana	View Answer on Stackoverflow

Why are AngularJS $http success/error methods deprecated? Removed from v1.6?

Angularjs Problem Overview

Angularjs Solutions

Solution 1 - Angularjs

Solution 2 - Angularjs

Apache Spark -- Assign the result of UDF to multiple dataframe columns

Cannot drop table users because other objects depend on it

Attributions