Private Extension my own python code

Development
,
8

Hello again

Unfortunately, since the slicer version has been unified( in my company), it cannot be changed.
There is no problem with this configuration in my version either.
The current problem situation is that the problem occurs from the moment the custom code is added.
I temporarily solved the problem by replacing it with a method of adding code through the ‘Ctrl+r’ short cut key, but I’m still curious about the sure method for the extension.

The above structure is automatically formed after the ‘Create Extension’ and ‘Add module to entension’ processes.
If so, where is your custom code included in the structure above?
In my slicer, I included my custom code directly in the directory after the above structure was created automatically.

like this

/tmp/TestExtension/
├── CMakeLists.txt
├── TestExtension.png
└── TestModule
    ├── CMakeLists.txt
    ├── __pycache__
    │   └── TestModule.cpython-39.pyc
    ├── Resources
    │   ├── Icons
    │   │   └── TestModule.png
    │   └── UI
    │       └── TestModule.ui
    ├── Testing
    │   ├── CMakeLists.txt
    │   └── Python
    │       └── CMakeLists.txt
    └── TestModule.py
    │
    └── my_custom_code.py (new !)

The part I found odd in the previous question is the ‘TestModule’ part.
This part is the output of the ‘Add module to extension’ process, I thought I was adding my custom code here, but it actually seemed to create a dummy folder.
Is it correct way to add custom code additions directly under these dummy modules?