dialog.js | 移动端Dialog弹出对话框插件，同时支持jQuery和Zepto

It looks like you already know how to make the user state a parameter of your main dialog's constructor. You can do the same in your cancel and help dialog's constructor, and pass the user state to it when you call super.

https://developer.mozilla.org/docs/Web/JavaScript/Reference/Operators/super

My question is how to achieve this in functional components ?

The fundamental answer there is: By writing a hook. There are a dozen different ways you could write this specific hook, but here's one example:

By default, JavaScript files imported from QML share their context with the QML component. If you remove the .pragma library from your JS file, the code behaves the same as if the JS code is run in your main QML file because they share the same context. So, why does .pragma library affect this? .pragma library creates a singleton-like JS file, and because any QML file can access it, its context is generically set to the root context or some top-level orphan context (not sure, could not determine from docs), not the context of the file that calls it.

From context documentation:

While QML objects instantiated in a context are not strictly owned by that context, their bindings are. If a context is destroyed, the property bindings of outstanding QML objects will stop evaluating.

I believe what you are seeing is the opposite of the second sentence, where the root context owns the bindings of your popup, and is calling its onClosed signal after its destruction.

So, your two scenarios described:

First Scenario:

1. Popup created, assigned applicationWindow parent, its creation context matches applicationWindow
2. Window closed, applicationWindow destruction starts
3. Because popup is child of applicationWindow, it is destroyed
4. applicationWindow context is destroyed, bindings stop being evaluated
5. popup closed signal is not called because its creation context was destroyed, no error thrown

Second Scenario:

1. Popup created, assigned applicationWindow parent, BUT its creation context is the root context
2. Window closed, applicationWindow destruction starts
3. Because popup is child of applicationWindow, it is destroyed
4. applicationWindow context is destroyed
5. after applicationWindow destruction, popup closed signal is called because its (root) creation context still exists, error is thrown because references in the signal handler have been destroyed

Probably the best way to solve this is to not use .pramga library in JS files that manage object creation. Otherwise, it is not a particularly worrisome error as it is smart enough to know the reference has been destroyed and doesn't access freed memory. You can get rid of the error by checking if (view) before calling view.destroy()

change permissions to PERMISSIONS in permissionCheck function

this is a problem with native-base DatePicker implementation, you can find a workaround here https://github.com/GeekyAnts/NativeBase/issues/3381#issuecomment-791300821 or use react-native-datepicker directly

I think your click event is propagating up the elements, and triggering onCloseHandle on your .dialog-wrap.

The simplest solution to this would be to use Event.stopPropagation() on the

E.g.

Looking at the Core Bot sample you can see that CancelAndHelpDialog is a component dialog, which means it has its own dialog set that we can add dialogs to. In your case you'll want a confirm prompt and a waterfall dialog. You can use BookingDialog as a guide for how to implement this because it extends CancelAndHelpDialog and therefore extends ComponentDialog.

You can see that BookingDialog adds inner dialogs to its dialog set in its constructor:

Constructors of UI5 classes should avoid arrow functions:

I notice that your Login component is a class, while the child FormDialog component is a function component using Hooks. There's nothing wrong with that, in itself - particularly if you started with an application using all class components and are slowly converting your components. But I detect some confusion here, because your function component seems to assume it's a class, in a sense. When you need to do things a bit differently.

Specifically, you reference this.login in your function component - but this is meaningless. login is passed in as a prop. In a class component, you would reference it as this.props.login. This doesn't work in a function component - but this.login isn't the substitute. Indeed this will tend to be undefined so this would even give an error. Even if not, it's not correct.

All you need to do is to make use of the argument to your function component - this is where the props object "lives" in a function component. You happen to ignore it by not using any arguments - but you don't have to do this.

So in short, what you need to do is:

1. replace export default function FormDialog() with export default function FormDialog(props)

2. replace this.login with props.login

3. repeat 2) for all other props which you have referenced using this