openproject/frontend/app/components/work-packages/wp-display-attr/wp-display-attr.directive.html

<span>
  <span class="wp-table--cell-span inplace-edit--read-value--value __d__cell" >

    <span class="__d__renderer inplace-edit--read-value--value-span">
      <ng-include ng-if="::!$ctrl.field.isManualRenderer"
                  src="::$ctrl.field.template">
      </ng-include>
    </span>

  </span>
</span>
remove class that is then replaced Because of the use of replace: true within the wp-display-attr, the classes of the first element get merged with whatever classes are defined on the calling dom element. As the classes on the calling dom elemnt suffice, we do not need that extra class. 9 years ago			`<span>`
remove wpEditField dependency from wpDisplayAttr 9 years ago			`<span class="wp-table--cell-span inplace-edit--read-value--value __d__cell" >`
Only display done ration as progress bar in work packages table 11 years ago
Fix broken styling of macro erros in WP overview 8 years ago			`<span class="__d__renderer inplace-edit--read-value--value-span">`
WIP reducing watcher count 9 years ago			`<ng-include ng-if="::!$ctrl.field.isManualRenderer"`
remove wpEditField dependency from wpDisplayAttr 9 years ago			`src="::$ctrl.field.template">`
			`</ng-include>`
WIP reducing watcher count 9 years ago			`</span>`
WIP reducing watcher count 9 years ago
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			`</span>`
Enable formatting for work package group headers in angular table 11 years ago			`</span>`