Closed HeleneAmouzou closed 3 weeks ago
🔎 A preview has been automatically published : https://clever-components-preview.cellar-c2.services.clever-cloud.com/cc-tile-requests/state-migration/index.html.
This preview will be deleted once this PR is closed.
Here are some thoughts on the empty state tile-metrics
vs tile-requests
:
tile-metrics
has a smart whereas there's none for tile-requests
tile-metrics
has three cases for emptiness :
tile-metrics
behavior.tile-requests
, but someday if we do implement one, I'll definitely go this way.Conclusion/TL;DR: In my opinion, there's no correct answer. However, I do like the cc-tile-metrics
way as it's the smart responsibility to handle and calculate its state, the component should only apply its state and not calculate it, it's simply not its job.
Maybe, if we had to make a compromise we could do it the other way around first and when we'll have a smart someday, go for this solution. :man_shrugging:
I'm sorry @florian-sanders-cc and @HeleneAmouzou that's not a clear yes or no. :sweat_smile:
empty
statesConsidering @Galimede's inputs, we have decided that it made more sense to leave the cc-tile-metrics
component unchanged and remove the empty
state from cc-tile-requests
.
The main reason is that the cc-tile-metrics
requires some logic to determine whether the state is empty or not and we prefer leaving it to the smart while cc-tile-requests
is more straightforward so the logic may remain within the component itself.
🔎 The preview has been automatically deleted.
🔎 A preview has been automatically published : https://clever-components-preview.cellar-c2.services.clever-cloud.com/cc-tile-requests/state-migration/index.html.
This preview will be deleted once this PR is closed.
What does this PR do?
cc-tile-requests
component to implement our new state structure,cc-tile-requests
component and its stories.How to review?