مسارات التنقل البرمجية

Sometimes a tap is not enough. After saving a form you may want to jump screens yourself. SwiftUI lets you drive the stack from code. ⚙️

Give NavigationStack a path binding. This array is the live list of screens currently pushed, and editing it changes navigation instantly.

Append a value to the path and SwiftUI pushes the matching screen. No tap needed, just change the array.

A navigationDestination maps each value type in the path to a view, so appended data knows which screen to become.

Removing the last element pops a screen, exactly like the back button. You stay in full control of the stack from code.

To return all the way to the root, empty the path. Every pushed screen disappears at once, perfect for a Done button. 🏠

Because the path is just data, you can build it from a URL or notification, pushing several screens so users land deep inside the app.

A NavigationPath can store values of different types together, letting one stack route books, users, and settings without a shared enum.

If every screen shares one type, a plain typed array works as the path and reads a little more clearly than NavigationPath.

Navigation becomes state. The visible screens always mirror the path array, so your UI stays predictable and easy to reason about.

Since the path is plain data, you can save it and restore it, recreating exactly where the user left off when they reopen the app.

What happens when you append a value to a NavigationStack path?

You bind a path to NavigationStack and push or pop screens by editing that array, turning navigation into predictable, testable state. 🎉