Table Component : add column labels

[PCo74]

To enable a small localization system in table component, can we add a top-level parameter to define column labels? (e.g. «col_labels»)

In table.handlebars, update :
line 48
<button class="table-sort sort d-inline" data-sort="{{@key}}">{{default (lookup ../../col_labels @index) @key}}</button>
line 50
{{default (lookup ../../col_labels @index) @key}}

select 
    'table' as component,
    TRUE as sort,
    --json_array("Prénom", "Nom", "Pseudo") as col_labels;
    --json_array("Vorname", "Nachname", "Pseudonym") as col_labels;
    json_array("nombre", "apellido", "seudónimo") as col_labels;

select 
    'Ophir'   as firstname,
    'Lojkine' as lastname,
    'lovasoa' as Pseudonym;
select 
    'Linus'    as firstname,
    'Torvalds' as lastname,
    'torvalds' as Pseudonym;

[lovasoa]

Hello and welcome to SQLPage !

A pull request for this would be welcome. The most important would be to document it clearly with examples.

Alternatively, you can also achieve programmatic column labels using the dynamic component. Here is an example of how to use it for translations:

select 'table' as component;
select
  'dynamic' AS component,
  json_group_array(json_object(
    (select target from translations where lang=$lang and source_en='name'), name,
    (select target from translations where lang=$lang and source_en='description'), description,
    (select target from translations where lang=$lang and source_en='price'), price
  )) AS properties
FROM products;

Screencast.From.2025-07-24.21-05-10.mp4

you can avoid the repetitions by creation an sql function like

CREATE OR REPLACE FUNCTION t(lang_code TEXT, source_text TEXT)
RETURNS TEXT AS $$
SELECT target FROM translations WHERE lang = lang_code AND source_en = source_text;
$$ LANGUAGE SQL IMMUTABLE;

this example uses the postgresql syntax

[PCo74]

Ok, thank you for this response that proposes a complete solution (source available in the examples?)
And bravo for your work !