![]() * Returns the ValidationResult returned by the TagPropertyValidator or null if no TagPropertyValidator * Validates the specified TagProperty with the TagPropertyValidator registered for it. ** Interface used for validating the properties of an EditableTag. Instant(key: string|Array, interpolateParams?: Object): string|Object * the get() method instead, which will return an observable that reacts to language changes. * This method only returns the translation for the currently selected language. * This method works like TranslateService.instant() of ngx-translate ( ). Get(key: string|Array, interpolateParams?: Object): Observable * An Observable with the translated value(s). * This method works like TranslateService.get() of ngx-translate ( ). * Gets the translated value(s) of the specified i18n key(s) for the currently active UI language. * to obtain translations for i18n keys that come from the GCMS UI. * This should be used in custom TagEditors and custom TagPropertyEditors ** An extension of Tag (see docs in REST API) with properties needed by the TagEditor */Įxport interface EditableTag extends Tag ): Promise ** Properties of the tag (representing the values in Gentics CMS) */ * Represents a Tag in a page or template or an object property. ** Maps keys to their respective TagProperties in a Tag. ![]() * The other properties depend on the TagPropertyType ( ). * This interface contains only the properties, which are always present. * Describes the value of a TagPart in a Tag. If you want to get started already, please copy the definitions from this page or for the model types, please refer to the data types used in the REST API.īoth custom editor types rely on these common model type interfaces in addition to the REST API model types: We will soon publish an npm package with the interfaces for the custom editors and the model types. The interfaces are provided on this page in their original TypeScript versions, but you can of course implement them with plain JavaScript as well. You only need to package it as static files in a DevTool package in order to deploy the custom editor to the CMS server.Įach custom tag property editor or custom tag editor needs to implement a specific interface to be integrated into the tag editor. html file with JavaScript or as an elaborate Angular or React app. Each of these can be realized as a simple. Instead of custom form TagParts, the new tag editor provides two well defined extension mechanisms, custom TagProperty editors and custom tag editors. In the new tag editor a TagPart can be hidden by checking its “Hidden in editor” property. 3 Hiding TagPartsĪ common use case for custom form TagParts was to hide certain TagParts in the tagfill. This can be done in the properties of the TagType. As long as a TagType relies on a custom form TagPart, it should be excluded from opening with the new tag editor. 2 Exclusion of TagTypes with CustomForm TagPartsĬustom Form TagParts are not supported by the new tag editor, instead it supports well defined extension mechanisms. Then right click on each node, where you want to use the new tag editor, select “Features”, and check the box for the “New Tageditor”.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |