8 Commits (a4c7c6c55512e25a023a148d174a43c9502236a2)

Author	SHA1	Message	Date
ulferts	48ac7aa6f4	introduce strategy for displaying fields (#4469) ... In order improve the code structure and in order to enable plugins to add display strategies for fields, that are not covered by the core yet, a strategy pattern is introduced for displaying fields. The mechanism is identical to the way EditFields are handled. In fact, the DisplayFields and EditFields now inherit from a common superclass, Field. Also, the service and the factory inherit from a common superclass.	9 years ago
Oliver Günther	ef94a15660	[23120,23121] Add required fields, labels to wp-edit-fields (#4421) ... * Add default label (name) to fields * Mark fields as required when schema says so * Work around xvfb :invalid state	9 years ago
Oliver Günther	a1445dffe6	Add field-controls for wiki-textarea field	9 years ago
Alex Dik	0f5219f6af	Fix TypeScript console output	9 years ago
Alex Dik	e14d57e571	Get rid of op.HalResource type definition	9 years ago
Oliver Günther	f27561fece	Allow plugins to receive field classes ... Costs cannot directly import, e.g., the SelectField, so we want the service to be able to return the registered classes in order for Costs to register the SelectField for a new type (costObject).	9 years ago
Oliver Günther	f3b175116c	Fix webpack typing warnings	9 years ago
Alex Dik	4a9702f614	Move the wp-edit-field files in their own directory	9 years ago
Alex Dik	93e75bd793	Implement a wpEditField service	9 years ago
Alex Dik	e8132be44b	Rename the select field's allowedValues property to options	9 years ago
Alex Dik	fcc2cd39a6	Implement first version of the WP edit module ... Disable links in the WP td directive as to prevent opening the details view. Also disable the table single-click handler to prevent confusion. This actually might be introduced back again, but can stay disabled for development.	9 years ago