Rework front modules

[DamnClin]

I think front modules needs to be reworked to have an example of what can be done frontend wise.

I made a small attempt here: https://gitlab.com/damon.colin/jhlite-vue-rework

I am calling a public API, I'd like to find some business operation to do on the frontend to make the example more appealing but can't come with a good idea for that right now

What do you think of this result?
cc @qmonmert @Gnuk @murdos @pascalgrimaud

[Gnuk]

It seems to have a good architecture. Actually I've updated the library (using a real book library web service) I've made with Tlaop using React here : https://github.com/Gnuk/library-hexa-react

I've added a Vue adapter to have multiple examples.

The library is the only part using hexagonal architecture.

Your architecture seems really similar.

[Gnuk]

The more business idea we want to do with Tlaop was something to represent a favorite, maybe it's also possible to rate a book.

And we can also do adapters only locally with localstorage for example in order to have other repositories than HTTP.

Maybe it's also possible to add a logic with events to see a primary adapter listening the event like a toast.

[murdos]

I agree that front modules can be improved, and that an example is useful.

I'm fine with the src/main/webapp structure.

I've a small suggestion regarding frontend component tests: IMO we don't need the infrastructure/primary subdirectories. Just specs/home/Home.spec.ts or specs/Home.spec.ts: just like cucumber tests in the feature directory, you're always addressing primary ports, and you would like to describe thinks in a user-friendly way, so it's not necessary to repeat the implementation tree structure.