Charlie Mordant

@deepu105 I get why the react-jhipster is complaining: some form React elements of the library are manipulating states and effects within the library itself, which is considered as a bad...

Created a branch with the current library achievement https://github.com/Tcharl/react-jhipster/tree/sort_non_paginated https://github.com/Tcharl/generator-jhipster/tree/sort_react I made a bit of progress, but still some work to achieve

Just a remark on the syntax: most of the methods are using the 'Each' keyword to tell that this method to specify that it will impact the whole entity pool....

node_modules contains the packages that bootstraps jhipster itself: don't worry with this one, it's only used for build. which profile are you talking about? I only see spring and maven...

For processing and technology specific methods, I encourage to move to a more object-oriented approach with packages and classes located in `/utils//`.

Too fast!

@amatosg You should create a new ejs file and also reference it in the according section of the relative 'file.js'

you can tweak the memory param in the `task integrationTest` plugin section of the gradle files (`build.gradle` or `gradle/profile_.gradle`. We had to find a tradeoff for memory usage to constrained...

@egvimo if you ever find this leak please fix! I wasn't 100% sure when implementing this class and there are not that much samples of usage in there...

> > I'm pretty convinced that UI improvement would boost jhipster adoption. > > UI generated by JHipster is mostly no longer relevant due to lack of good tables. >...