Michael Krecek

@mvorisek Just some further food for discussion to make uses cases a bit clearer: 1. Let's say a user has restricted access to only some customer entities - e.g., he...

@mvorisek That sounds practical to me and very logical. Any other thoughts from the community @DarkSide666 eventually? What about the idea of weak conditions (so we would not completely clear...

@DarkSide666 Same here - I use them a lot to save lines of code when defining Models.

@mvorisek I have two areas where i use addFields: 1) In Model::init to define a lot of fields quickly, so addFields(['name', 'created_date' => ['type' => 'date'], ...) This saves having...

Form's save button: https://github.com/atk4/ui/blob/01d39d24694e4b4f63a576d090e55e0e97aaa9e4/src/Form.php#L76 EceutorFactory: https://github.com/atk4/ui/blob/01d39d24694e4b4f63a576d090e55e0e97aaa9e4/src/UserAction/ExecutorFactory.php#L56

We should then remove the default in the property definition and load it in the init function by checking if _t function is null or otherwise set to 'Save' in...

By fallback you mean, that it is only replaced if not yet set? Grammar and replace in rendering sounds also very elegant. Your take, what coding structure would work best....

Agree - any way to open up translation possibilities is better than what we have today. I think singular/plural things are very well considered if you look in atk4/i18n or...

Atk4/i18n is a wrapper for Symfony\Translation made by @ibelar - this supports pattern translations, and also simple logic like male/female or other conditional texts. I'd think this is using Symfony/Translation...

If we can achieve where today hardcoded strings are present, instead - if defined - a translate function is called passing an id like `form.button.save` as parameter and checking if...