Feature: opionated sequence of middlewares and tasks

[uxkjaer]

When you are sorting out your tooling some extensions needs to go before others. I think the best of ui5 site would be a good place to keep a central list of the order of how extensions should be implemented instead of all being after a standard process. I would be able to leverage this in the generator as well. I will start on a local one for my demo, but it would suit better with a spot in this repo.

[marianfoo]

For example, for a custom control, do you mean implementation with a library or just a file.
I guess you want to automate this similar to the generator and have a selection of packages that can then be automatically integrated into an app?
In my opinion, this is relatively simple via NPM. Then only a few lines in yml and package.json are missing.

Can you please describe your requirements in more detail.

[petermuessig]

Why not sorting the packages by the downloads of the last 14 days? The data is part of the bestofui5-data and you can do the sorting on your own. WDYT?

[marianfoo]

Every package has some attributes you can sort by (i do that in the frontend):

What other kind of attributes are you looking for?

[uxkjaer]

I'm more talking about a sequence of how middleware and tasks should be added into the ui5.yaml file, this should be seen as a best practice on how the extensions are guaranteed to work best with each other. For example onelogin package should come before any proxy to add the cookie.