Marcelo Shima

https://github.com/jhipster/generator-jhipster/blob/2b98ce8cb2b418ffeb1e4965388d88628767c2b7/generators/entity-client/templates/react/src/main/webapp/app/entities/entity.reducer.ts.ejs#L69 https://github.com/jhipster/generator-jhipster/blob/2b98ce8cb2b418ffeb1e4965388d88628767c2b7/generators/entity-client/templates/react/src/main/webapp/app/entities/entity.reducer.ts.ejs#L80 We can remove others functions warnings by changing. https://github.com/jhipster/generator-jhipster/blob/2b98ce8cb2b418ffeb1e4965388d88628767c2b7/generators/entity-client/templates/react/src/main/webapp/app/entities/entity.reducer.ts.ejs#L90-L97 To ``` async (entity: I, thunkAPI) => { const result = await axios.post(apiUrl, cleanEntity(entity)); thunkAPI.dispatch(getEntities({})); return result; ```

@mraible in any case, the search api looks wrong, it should fix it for microfrontends.

Using gateways user api is the current design, it fetches from gateway and cascades the user relationship.

It's possible to drop consul-loader docker image?

> @mshima With liquibase 4.14.0, autoincrement have been fixed for mysql/mariadb/h2 (see [here](https://github.com/liquibase/liquibase/pull/3026)) Do not remember if we should make any changes here: > > https://github.com/jhipster/generator-jhipster/blob/d048756de18718433196c78c7703c4f37cfdeafd/utils/field.js#L282-L298 Not needed.

Try updating h2-r2dbc

Maybe we should try to update h2 only at imperative

@DanielFran tests succeeded.

blog application is missing clientFramework, so it's not a microfrontend. gateway is using react, store is using angular, mixing client frameworks is not supported.

> > blog application is missing clientFramework, so it's not a microfrontend. gateway is using react, store is using angular, mixing client frameworks is not supported. > > Isn't this...