Localization keys should also accept functions instead of just strings

[gaspardip]

Title basically, I want to be able to do

const localization = {
    selectedCountOfRowCountRowsSelected: ({ selectedCount, rowCount }) => `${selectedCount} de ${rowCount} fila(s) seleccionadas`
}

This gives users a lot more flexibility about their translations.

A few use cases are

• Pluralizing strings
• Dynamic strings

[KevinVandy]

Possibly a good idea, though you can get access to the state by hoisting, or looking at the tableInstanceRef to get those parameters. See here

[KevinVandy]

Would you be interested in helping with a PR if going this route? I think I might have to make it so that it accepts a string or a function for each translation with vars

[gaspardip]

Yeah, give me a few days, I can create a PR.

[gaspardip]

Were you thinking of doing it at the component level or use a context provider and consume it in the respective components?