imodel-browser-react: export BaseCard component

[ImVeryLost]

My project contains a grid that is for "non iTwin/iModel items". As such, i don't want to use the iModelGrid/iModelTile/etc.

But i still want to have a consistent UI across all grids, without worrying that an update to imodel-browser-react will make things look out of sync.
I would like to be able to simply use BaseCard and build the grid on top of it.

[ben-polinsky]

Makes sense, LGTM.

[alexdunae]

My concern with exporting BaseCard is that it commits the admin-components package to a public API that wasn't particularly vetted.

Going through the list, though, most of the prop names are generic enough to not be controversial.

Can we rename the statusIconHref prop . (title left icon? title icon?, just icon?). UX hasn't given clear direction on what each of the customization points is meant to be used for, so calling it "status" doesn't feel accurate.

[ImVeryLost]

My concern with exporting BaseCard is that it commits the admin-components package to a public API that wasn't particularly vetted.

Going through the list, though, most of the prop names are generic enough to not be controversial.

Can we rename the statusIconHref prop . (title left icon? title icon?, just icon?). UX hasn't given clear direction on what each of the customization points is meant to be used for, so calling it "status" doesn't feel accurate.

Agree that there are implications to publishing a component that was previously used internally only. Some notes:

1. The component is already marked as alpha, and the component documentation makes it clear that it's "a building block". I hope that is enough to deter 'casual use', but I'm open to suggestions on how to update the docs to make it clearer.
2. I'm not sure i would call it "non vetted" - it's used by the two main tiles (iModelTile and iTwinTile), which ensure that BaseCard is consistent in UI and functional.
3. statusIconHref is already exposed in the iTwin/iModel tiles, so i would rather not rename it: