feat(Team Dashboard): Temporarily hide team stats block

[HenerHoop]

https://app.clickup.com/t/86ayqffyf

[github-actions]

size-limit report 📦

Path	Size
packages/cxl-ui/pkg/dist-web/cxl-ui.js	66.98 KB (+0.17% 🔺)
packages/cxl-ui/pkg/dist-web/cxl-ui-jwplayer.js	11.87 KB (0%)
packages/cxl-ui/pkg/dist-web/cxl-ui-playbooks.js	27.77 KB (0%)
packages/cxl-ui/pkg/dist-web/vendor.js	135.58 KB (0%)
packages/cxl-ui/pkg/dist-web/cxl-ui-jwplayer.js, packages/cxl-ui/pkg/dist-web/cxl-ui-playbooks.js, packages/cxl-ui/pkg/dist-web/cxl-ui.js, packages/cxl-ui/pkg/dist-web/manifest.js, packages/cxl-ui/pkg/dist-web/unresolved.js, packages/cxl-ui/pkg/dist-web/vendor.js	243.35 KB (+0.05% 🔺)

[pawelkmpt]

Commit message

- feat(Team Dashboard): Temporarily hide team stats block
+ feat(cxl-ui): cxl-dashboard-team-stats add hide progress, stats properties

---

I flipped the logic to make it a bit clearer. Instead of show, it's now hide.

IMO using
${this.showProgress ? html`` : nothing

is easier to read than
${!this.hideProgress ? html`` : nothing

but let it stay and not waste time on opinions ;)

[HenerHoop]

Commit message

- feat(Team Dashboard): Temporarily hide team stats block
+ feat(cxl-ui): cxl-dashboard-team-stats add hide progress, stats properties

I flipped the logic to make it a bit clearer. Instead of show, it's now hide.

IMO using ${this.showProgress ? html : nothing ``

is easier to read than ${!this.hideProgress ? html : nothing ``

but let it stay and not waste time on opinions ;)

I agree with you. From a developer's perspective, it might be a bit harder to read, but in terms of overall logic, it seems more logical to me that the element is visible in normal situations, and then we want to hide it in certain cases.

[pawelkmpt]

@HenerHoop conflicts appeared after merging #361. Please resolve them