List like transitions for VStacks?

transition.swift

import Foundation
import SwiftUI
import PlaygroundSupport

let allTexts = ["one", "two", "three", "four", "five"]
let selectedTexts = ["two", "four"]

struct TestView: View {
    
    @State private var expanded = false
    
    var body: some View {
        VStack { // <- Replace with "List" to see what I want
            ForEach(expanded ? allTexts : selectedTexts, id:\.self) { text in
                Text(text)
            }
        }
        .animation(.default, value: expanded)
        .onTapGesture { expanded.toggle() }
        .frame(width: 300, height: 600)
    }
}

PlaygroundPage.current.setLiveView(TestView())

I think I got a solution that (sort of) does what I want without rewriting VStack. The idea is to not have SwiftUI show/hide elements based on ID, but to always show them and alter their size/opacity. That way, the origin position is not static in the animation but close to the nearest visible element.

import Foundation
import SwiftUI
import PlaygroundSupport

let allTexts = ["zero", "one", "two", "three", "four", "five", "six"]
let selectedTexts = ["two", "four"]

struct TestView: View {
    
    @State private var expanded = false
    
    var body: some View {
        VStack(spacing: 0) {
            ForEach(allTexts, id:\.self) { text in
                let visible = selectedTexts.contains(text)
                Text(text)
                    .frame(height: expanded||visible ? nil : 0)
                    .opacity(expanded||visible ? 1 : 0)
                    .transition(.opacity)
            }
        }
        .listStyle(.plain)
        .onTapGesture { expanded.toggle() }
        .border(.red)
        .clipped() // <- Using `clipped` shows what the issue is. It is irritating that "One" and "Five" don't move.
        .animation(.spring(), value: expanded)
        .frame(width: 300, height: 600)
    }
}

PlaygroundPage.current.setLiveView(TestView())

I wanted to propose that but thought that if allTexts and selectedText change with a common addition the common addition would animate in in the undesired way. But if that won't happen, then I think that solution looks really nice.