Set up search states and base components

[tkohr]

This PR intends setting up a base that allows to create the various metadata record lists in different layouts.

• it introduces three search states
  • a mainSearch state for the results grid, bound to the router
  • a headerHome state via a directive for the last created record, displayed in the home header
  • a headerSearch state via a directive for the favorite records, displayed in the search header
• it adds two different results-list components based on a common base component (allowing to implement different layouts)
  • mel-datahub-results-list-carousel
  • mel-datahub-results-list-grid
• it adds three different results-list-item components based on a common base component (allowing to implement different layouts)
  • mel-datahub-results-card-favorite
  • mel-datahub-results-card-last-created
  • mel-datahub-results-card-search

[fgravin]

There are some residual component files, you should use the nx cli to create the structure and the components.

For the state search it looks good 👍

For the file structure, it's ok, you could have put some UI components in the dedicated page folder but's it's kifkif

Think of embracing ng17 nex features though 😏

[fgravin]

Those files are not used, how do you generate your components ?

[tkohr]

Right, I oversaw this one after creating the extends

[tkohr]

Thanks for your feedback @fgravin !

There are some residual component files, you should use the nx cli to create the structure and the components.

Correct, I didn't pay attention to this, should be cleaner now.

For the file structure, it's ok, you could have put some UI components in the dedicated page folder but's it's kifkif

Yep, I chose to put all results-list and results-list-item components in common as they will be easier to find and combine IMO.

Think of embracing ng17 nex features though 😏

Noted 👍