Initial Reactive support

[cbornet]

• Please make sure the below checklist is followed for Pull Requests.

• Travis tests are green

• Tests are added where necessary

• Documentation is added/updated where necessary

• Coding Rules & Commit Guidelines as per our CONTRIBUTING.md document are followed

First basic implementation of reactive option.
The experimental flag must be set to see the option in the questions.

See #7608

[jdubois]

@cbornet you have Travis work with Reactive???

[cbornet]

Yes, I do 😄 !
I'll be AFK for 3 weeks (at least) so it would be great if this could be reviewed and merged meanwhile. Or at least don't do any big bang refactoring during this period so it's not a nightmare to rebase 😅
Don't hesitate to fix directly on the branch if needed.

[pascalgrimaud]

as always, incredible work @cbornet ! 😮

[cbornet]

I force pushed one last time because I had done a mistake in the last commit. I won't do it again, I promise.

[joumenharzli]

The last time i used webflux i found that Springfox is not willing at this time to support it. So i cannot use it to document my apis.
springfox/springfox#1773 (comment)
What will you plan for Swagger ?

[cbornet]

I think Springfox's maintainer is working actively on supporting Webflux. It seems like a lot of work and I'm sure he would love to get help. Unfortunately I have so much to do right now that I can't help him myself.
I guess we'll have to wait for now. But don't worry there's already plenty of work around Webflux for Jhipster.
As for the Api-first option, it shouldn't be hard to do in case you're also using it.

[DanielFran]

@cbornet @joumenharzli see springfox/springfox#2608

[DanielFran]

@cbornet @joumenharzli see springfox/springfox#2608 has been merged! :)

[cbornet]

Is there any objection to merge once I resolve the conflicts ?

[jdubois]

@cbornet no, because I don't think this would have any impact with the rest of the code, so there's no risk

[cbornet]

OK so I'll proceed. After that we can do more atomic PRs.

[deepu105]

@jdubois IMO this ticket needs more than a 100$ bounty, may be we should multiply bounty based on complexity of the ticket since not every ticket are the same

[jdubois]

Yes this is like the VueJS bug bounty. The "lead" of each project (so @cbornet here) should create a project and split the main issue into several issues. Then we'll add bounties to those tickets: like for VueJS, I think we should give at least $500 here, so that means 5 tickets will have each a $100 bounty.

That's also better because maybe several people will work on the project, so that's a way to split the money between contributors.

[deepu105]

Ya that sounds fine Thanks & Regards, Deepu

…

On Wed, Aug 29, 2018 at 11:31 AM Julien Dubois ***@***.***> wrote: Yes this is like the VueJS bug bounty. The "lead" of each project (so @cbornet <https://github.com/cbornet> here) should create a project <https://github.com/jhipster/generator-jhipster/projects> and split the main issue into several issues. Then we'll add bounties to those tickets: like for VueJS, I think we should give at least $500 here, so that means 5 tickets will have each a $100 bounty. That's also better because maybe several people will work on the project, so that's a way to split the money between contributors. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#7983 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABDlF58CuniSwOg3vy-n8GtXT2qC38Ztks5uVl95gaJpZM4VRrJh> .

[Mahdihp]

added Reactive support webflux with jwt

[jdubois]

@Mahdihp that's the third comment you post in a row which doesn't make much sense, what's happening?