SwiftUI Struct for Dictionary entry

If I'm understanding correctly, you are looking to

1. Take some user input
2. Transform that into keys that correspond to your data dictionary
3. Extract the data for the matching keys into some struct
4. Display a list of those structs using SwiftUI

Here is a simple implementation of those steps.

import SwiftUI

// A dictionary containing your data
let data: [String: Int] = [
    "apples": 5,
    "bananas": 3,
    "cherries": 12
]

// A struct representing a match from your data
struct Item {
    var name: String
    var quantity: Int
}

// A view that displays the contents of your struct
struct RowView: View {
    var item: Item

    var body: some View {
        Text("\(item.quantity) \(item.name)")
    }
}

struct ContentView: View {
    @State private var searchText: String = ""

    func items(matching search: String) -> [Item] {
        // 2 - split the user input into individual keys
        let split = search.split(separator: " ", omittingEmptySubsequences: true).map { $0.lowercased() }
        // 3 - turn any matching keys/values in your dictionary to a view model
        return split.compactMap { name in
            guard let quantity = data[name] else { return nil }
            return Item(name: name, quantity: quantity)
        }
    }

    var body: some View {
        VStack {
            // 1 - get user input
            TextField("Search", text: $searchText)
                .padding()
            // 4 - display the matching values using ForEach (note that the id: \.name is important)
            List {
                ForEach(items(matching: searchText), id: \.name) { item in
                    RowView(item: item)
                }
            }
        }
    }
}

You'll see that as you type in the text field, if you enter any of the strings "apples", "bananas", or "cherries", a corresponding row will pop into your list.

Depending on the size of your list, and what kind of validation you are performing on your users search queries, you might need to be a little more careful about doing the filtering/searching in an efficient way (e.g. using Combine to only split and search after the user stops typing).