Add support for function instead of string in name/description field …

[fookoo]

Description

Add support for function instead of string in schema object.

You can now use

let schema = {
        type: "object",
        properties: {
                name: {
                    type: "string",
                    minLength: 2,
                    title: () => $filter('translate')("Name"),
                    description: () => $filter('translate')("Description")
                },
                title: {
                    type: "string",
                    enum: ['dr','jr','sir','mrs','mr','NaN','dj']
                }
            };

Fixes Related issues

#754

Checklist

• I have read and understand the CONTRIBUTIONS.md file
• I have searched for and linked related issues
• I have created test cases to ensure quick resolution of the PR is easier
• I am NOT targeting main branch
• I did NOT include the dist folder in my PR

[Anthropic]

@fookoo thanks for the PR, can you see a way we could apply the solution to the form instead of the schema? schema-form is a standard we do not control and can't really make changes to while remaining compliant.

I love the approach and can see the need for it, but to be accepted it needs to be applied via the form javascript instead which is optional also.

[nicklasb]

Great functionality, but as @Anthropic said, should be applied to the form instead of the schema. To elaborate, JSF/ASF is all about separation of concerns, the schema exclusively defines structure and validation and the form exclusively defines the UI.

[Anthropic]

Closing due to lack of response, i18n has alternative suggestions for handling such as #865