Luc Claustres

I think there are some design choices here. It seems that cote components are not lightweight elements regarding discovery so that it's better to only have some per process. It...

Great work, many thanks ! Could you please update also the code snippets that are included in the README before merging because it seems that some should be changed as...

It seems there are a lot of missing files in the API like `index.js, app.hooks.js, logger.js, ...` and also config folder, will try to retrieve them from feathers sample chat...

Sorry can't yet merge this PR there is too much work remaining. I don't know how you could have tested it with missing files. Morevover you should have a look...

Now backend can at least run but not frontend, it appears most components like `Index.vue` and `Chat.vue` are missing, could you please add them back ?

You are fundamentally right, having everything in one place is the best, and when things tend to depend on some ordering yes unpredictability can occur when adding features. However in...

Just to be more clear, if the app holds all hooks then it is also required to hold all the services. In a microservice deployment this raises two issues I...

That's really interesting, jumping to a "hook tree" (I am not sure about a graph as you have to consider cycles, etc.) instead of a "hook chain" adds a level...

These patterns are useful and easily implemented with current Feathers, eg in our krawler tool we apply some metadata allowing to apply a hook only when hook data [match some...

Yes your anchor covers it, I was talking about the discussion between @eddyystop and @j2L4e