web: Better storage summary

[ancorgs]

Problem

When the configuration uses some feature not supported by the UI (like LVM or legacyAutoyastStorage), the storage section of the summary shows this message: "No device selected yet". Even if the configuration leaded to a valid storage setup.

Solution

Now the situation is properly handled and the message makes more sense.

[joseivanlopez]

NP: do we need to pass the model as prop? Just saying because after some discussions with @dgdavid, we decided that the components should recover all the info they need from hooks. But maybe in this case we want a component which is able to render different models?

[dgdavid]

Exactly. Somehow we realize that it's better having components able to query the information they need when possible instead of depending on the props of some parent. Not written in stone, of course, but thanks to the React Query cache most of times it works fine.

But maybe in this case we want a component which is able to render different models?

Good point.

[joseivanlopez]

What happens if there is a config with errors?

[ancorgs]

What happens if there is a config with errors?

Nothing special. The summary sentence simply explains what the configuration is about, it does not tell anything about whether is a good or bad configuration. That's the mission for the part of the interface displaying issues. That's not new in my PR, that's how the summary works.

So the only change here is to better handle the situation in which we cannot explain the configuration.

[dgdavid]

What happens if there is a config with errors?

Nothing special. The summary sentence simply explains what the configuration is about, it does not tell anything about whether is a good or bad configuration. That's the mission for the part of the interface displaying issues. That's not new in my PR, that's how the summary works.

So the only change here is to better handle the situation in which we cannot explain the configuration.

Exactly.

There is room for improvements, though. But it has to wait until reserving time for improving the overview page itself, where these summaries are being rendered right now.