Vert.x stack futurisation

[vietj]

This issue keeps track of the futurisation of the Vert.x stack, it's an umbrella issue

• milestone1
  • [x] vertx-core
• milestone2
  • [x] vertx-redis-client
  • [x] vertx-auth
  • [x] vertx-web
  • [x] vertx-bridge-common
  • [x] vertx-mqtt
  • [x] vertx-kakfa-client
  • [x] vertx-cassandra-client
  • [x] vertx-amqp-client
• milestone3
  • [x] vertx-circuit-breaker
  • [x] vertx-service-discovery
  • [x] vertx-config
• milestone4
  • [x] vertx-mongo-client
  • [x] vertx-stomp
  • [x] vertx-rabbitmq-client
  • [x] vertx-shell
  • [x] vertx-health-check
  • [x] vertx-mail-client
  • [x] vertx-sql-client
  • [x] vertx-consul-client

[cvgaviao]

in which moment of futurisation plan will the Future interface extend CompletionStage?

[vietj]

Hi,

I think that's something we can think about.

At the moment I would rather keep Vert.x Future as is and add a toCompletionStage method on it rather than extending it.

Julien

On 5 Aug 2019, at 17:48, Cristiano Gavião notifications@github.com wrote:

in which moment of futurisation plan will the Future interface extend CompletionStage?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/vert-x3/issues/issues/472?email_source=notifications&email_token=AABXDCQIL7BGTU2JWEYGU73QDBDUZA5CNFSM4H26DLE2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3SHTTY#issuecomment-518289871, or mute the thread https://github.com/notifications/unsubscribe-auth/AABXDCQSKB5ALG5EOAZ3FX3QDBDUZANCNFSM4H26DLEQ.

[tsegismont]

@vietj how about adding the toCompletionStage method in milestone4 ?

[vietj]

I would like actually to come up with several proposals for Future