ion-nav is a standalone component for loading arbitrary components and pushing new components on to the stack. It's not tied to a particular router, so this means that if we load a Nav component, and push other components to the stack, they will not affect the app's overall router. That's what this project has been about, avoiding Angular Router with interactions done via NavLink as a simplified API, and creating additional components which have been customized to pass data between multiple reactive forms when the user is moving forward though the application.
-
ion-nav-link component which has been wrapped up with a dynamic div to make it not clickable for the user while form is not active. This component is re-used in each form to make the magic happens when user wants to go forward in the App.
-
ion-modal component where final form is rendered with data set in all views by the user. This is just in use in a specific component(email component) so methods and data are linked using
Input()
,Output()
Decorators for transferring/detect data changing and modify the DOM.
Data service where a Subject(BehaviorSubject) is set with registering values when user submit a form in each view of the App. Then, the data is stored asObservable in a global variable, being able to get back those values from any level needed.
@angular/cli: "15.0.0"
rxjs: "7.5.0"
typescript: "4.8.4"
@ionic/angular: "6.1.9"
@capacitor/cli: "4.6.1"
JoseMMorales