Allowing functions for Schema messages
See original GitHub issueWhy can i give a function to a label, but not to an message? This currently doesn’t allow me to i18n the error messages like this:
regEx: [
{msg: function(){
return TAPi18n.__('forms.error.regEx.msg');
}
},
...
]
Issue Analytics
- State:
- Created 9 years ago
- Comments:8
Top Results From Across the Web
Creating and managing schemas | Cloud Pub/Sub ...
Validating message schemas · In the Google Cloud console, go to the Pub/Sub schemas page. · Select the schema you want to view...
Read more >Documentation: 15: CREATE FUNCTION - PostgreSQL
If a schema name is included, then the function is created in the specified schema. Otherwise it is created in the current schema....
Read more >Pass schema's context to validation functions #289 - GitHub
I am thinking about a way to pass context to validation function. Currently validation function expect exactly one argument, ...
Read more >Schema Registry Overview - Confluent Documentation
Schema Registry lives outside of and separately from your Kafka brokers. Your producers and consumers still talk to Kafka to publish and read...
Read more >Create User-defined Functions (Database Engine) - SQL Server
Requires CREATE FUNCTION permission in the database and ALTER permission on the schema in which the function is being created. If the function...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
True.
But i would even though appreciate if i could define global schema messages the same way i can define labels, using a function:
+1