@Harpush My team is using angular-split together with <ng-template>, which would not be supported after this update, after which the order of <as-split-area> elements as written in the HTML file trumps what's actually in the DOM

Example:

<ng-container>
  <as-split>
    <!-- Left-to-right -->
    <ng-container *ngIf="leftToRight; else rightToLeft">
      <ng-container *ngTemplateOutlet="areaOneTemplate; context: { order: 0 }"></ng-container>
      <ng-container *ngTemplateOutlet="areaTwoTemplate; context: { order: 1 }"></ng-container>
    </ng-container>

    <!-- Right-to-left -->
    <ng-template #rightToLeft>
      <ng-container *ngTemplateOutlet="areaTwoTemplate; context: { order: 0 }"></ng-container>
      <ng-container *ngTemplateOutlet="areaOneTempalte; context: { order: 1 }"></ng-container>
    </ng-template>

    <ng-template #areaOneTemplate let-order="order">
      <as-split-area [order]="order">
        Area One
      </as-split-area>
    </ng-template>

    <ng-template #areaTwoTemplate let-order="order">
      <as-split-area [order]="order">
        Area Two
      </as-split-area>
    </ng-template>
  </as-split>
</ng-container>

angular-split v18.0.0 (after removing [order]) will behave as if Area One is the first in the DOM, even if an right-to-left scenario, Area Two would be first in DOM

Angular 18 update #441

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions