bug: ion nav component

[EslamNemr]

Prequisites

• I have read the Contributing Guidelines.
• I agree to follow the Code of Conduct.
• I have searched for existing issues that already report this problem, without success.

Ionic Framework Version

• v4.x
• v5.x
• v6.x

Current Behavior

ion nav component with ionic/vue
when trying to pop to another view all forward views component in the stack didn't unmounted or removed from the dom which cause memory leak.
even using remove function just remove the view and didn't unmount or destroy the component and also didn't remove dom element

Expected Behavior

its should just keep the pervious element in the stack and remove or unmount all the forward.

Steps to Reproduce

1- add nav component and pop to any view
2- check dom elements still there
3- check vnode subtree or vue dev tool still unmounted.

Code Reproduction URL

No response

Ionic Info

No response

Additional Information

No response

[liamdebeasi]

Thanks for the issue. I am going to close this as a duplicate of #21831.

[EslamNemr]

i would like to leave my solution here for any one use ionic/vue nav component
in file
https://github.com/ionic-team/ionic-framework/blob/main/packages/vue/src/components/IonNav.ts

i return views which is the array of created component vnode as props then i managed to delete it from my component
it seems the bug in framework delegate and core component remove view function.

setup() {
const views = shallowRef([]);

/**
 * Allows us to create the component
 * within the Vue application context.
 */
const addView = (component: VNode) => views.value = [...views.value, component];
const removeView = (component: VNode) => views.value = views.value.filter(cmp => cmp !== component);

const delegate = VueDelegate(addView, removeView);
return () => {
  return h(
    'ion-nav',
    { delegate, views },
    views.value
  )
}

}
});

[ionitron-bot]

Thanks for the issue! This issue is being locked to prevent comments that are not relevant to the original issue. If this is still an issue with the latest version of Ionic, please create a new issue and ensure the template is fully filled out.