{"push_id":652344873,"size":2,"distinct_size":2,"ref":"refs/heads/field_definition_custom_templates","head":"25959cef72fb7d11417fad9fff9def78be0ed811","before":"c69f07827e79a2b7beff8b97c4413c991ca88100","commits":[{"sha":"5a3bbad4d48cb9ccfa6e9f40fd2f4b70dd39c509","author":{"email":"ca0794b6d6ec3d5c1d8d3acbaff6edcb7c650056@gmail.com","name":"Jérôme Vieilledent"},"message":"EZP-24304: Provide a way to customize field definition form views\n\n> https://jira.ez.no/browse/EZP-24304\n\nAdded `getFieldDefinitionEditConfig()` to FieldTypeFormMapperInterface.\nReturned value is a hash which may contain:\n* `template`: template where specific form fields defined in mapFieldDefinitionForm() will be displayed.\n* `vars`: Hash of additional variables to pass to the template.\n\nProvided template will be included during FieldDefinition rendering, in\norder to add potential additional fields.\nVariables passed to the form are:\n* `data`: FieldDefinitionData object\n* `languageCode`: Language code as passed to the main form\n* `contentTypeDraft`: The ContentTypeDraft object\n* `form`: Current FieldDefinition form\n\nNote that it is *not mandatory* to provide a template. If a FieldType\ndoesn't need additional form fields (i.e. no validator or field\nsettings), there is no need to define a template.\n\nAlso moved update_content_type.html.twig to ContentType subdirectory","distinct":true,"url":"https://api.github.com/repos/ezsystems/repository-forms/commits/5a3bbad4d48cb9ccfa6e9f40fd2f4b70dd39c509"},{"sha":"25959cef72fb7d11417fad9fff9def78be0ed811","author":{"email":"ca0794b6d6ec3d5c1d8d3acbaff6edcb7c650056@gmail.com","name":"Jérôme Vieilledent"},"message":"Added labels translation for ContentType","distinct":true,"url":"https://api.github.com/repos/ezsystems/repository-forms/commits/25959cef72fb7d11417fad9fff9def78be0ed811"}]}