Skip to content
This repository was archived by the owner on Apr 12, 2024. It is now read-only.
This repository was archived by the owner on Apr 12, 2024. It is now read-only.

Result of chained HttpPromise should be a HttpPromise and not a Promise #4345

Closed
@mren

Description

@mren

Hey.

If I chain two HttpPromise with

return $http.get('/foo').then($http.post('/foo'))

the return value is a Promise and not a HttpPromise.
If chained HttpPromises would still be HttpPromise their usage would be more consistent

Advantages:

  • Simple: On Success the next HttpPromise could be called directly with the body and not with {data, status, header, config}
  • Abstraction: Have all the power of Promises without missing out the features of HttpPromises
  • Consistency: Interacting with chained Requests would be in the same way as with a normal request

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions