96ba45b966
connectivity-list and data-tables had no profile meta at all, so the Studio and the gallery fell back to a humanised profile id: a reader picking a view saw "connectivity list" and "data tables" rather than what the pane actually is. The sibling connectivity-map already carried a label; these two are now in step, so the three read as one family in the picker instead of sorting apart. The wording is not invented. Each pane renders its own heading from i18n — connectivity.list.title is "Cities with Internet" and connectivity.tables.title is "Cities Data" — so the labels lead with the product name the reader already sees, then name the view, matching the shape connectivity-map established. Both metas declare stage experimental explicitly. That is the existing default for a profile with no meta, so nothing is promoted and the manifest is byte-for -byte unchanged; it is stated because bundleStage turns a whole bundle production as soon as one profile claims it, and a stage left implicit is one default change away from moving on its own. Source only, no bundle rebuild: the label is read from the meta by the gallery's discovery, and never travels into manifest.json.
5 lines
575 B
JSON
5 lines
575 B
JSON
{
|
|
"stage": "experimental",
|
|
"label": "Cities with Internet — data tables",
|
|
"note": "Label read by internal/plugin-gallery/discover.mjs (`meta.label || profile`); without a meta file this profile showed as the humanised id 'data tables'. The pane's own heading is t('connectivity.tables.title') = \"Cities Data\"; the label leads with the bundle's product name so the picker groups it with connectivity-map and connectivity-list rather than sorting it away under a different first word. stage declared explicitly for the reason given in connectivity-list.meta.json."
|
|
}
|